Opened 8 years ago

Last modified 8 years ago

defect #105 (closed: DONE)

Roadmap and iteration pages have ? and a red square for "sized" - is there a problem modifying completion stages after entering tickets

Test Complete Size: 3 Test Complete Date: 05/17/2009
Documentation Complete Size: 1 Documentation Complete Date: 05/22/2009
Acceptance Complete Size: 1 Acceptance Complete Date: 05/23/2009
Reported by: billyr Owned by: ja11sop
Milestone: Clean up of Plugin with Patch Component: agile-trac.org
Version: Keywords:
Cc: Blocked By:
Blocking: Patch SVN Revision:
Patch Trac Version: not_applicable
In Iterations: 22 23

Description (last modified by ja11sop) (diff)

First of all thanks for a great TRAC plugin, and brilliant presentation on the  Foundations of Agile Development.

I don't know the first thing about Python or trac plugins, but if there's an opportunity I'd be keen to help out with this plugin.

Ok on to the problem...

I set up trac, then the plugin, entered a bunch of stories, defects, etc, and then later changed the completion stages to: Build, Presentation, QA, Acceptance.

Looking at the Roadmap (or Iteration view) I have some tickets that are have been sized in all completion stages, but the far right overall size column still shows a question mark. What's weird is there are other tickets that do have a value in this overall size column and I can't see any difference between the tickets.

E.g. ticket 73:

  • is sized
  • is a defect
  • has sizes 0,1,1,1
  • shows an overall size of ? on the roadmap
  • belongs to a milestone, but not to an iteration yet

ticket 137:

  • is sized
  • is a defect
  • has sizes 0,1,1,1
  • shows an overall size of 3 on the roadmap
  • belongs to a milestone, but not to an iteration yet

Looking at more of the tickets, it seems like only the recent (higher number) tickets show the overall size figure, when all the sizes have been set.

Do you know what might be causing this problem?

Is the overall size calculated by adding up the sizes of the all stages or is there something else going on? For example I have another ticket that is 3,1,1,1 but it's overall size shows 10 (I was expecting 6).

I'm going to fire up a SQLite browser to see if I can spot the differences in the underlying data.

Thanks in advance!

System info:

  • Running on Windows via tracd standalone
  • Trac: 0.11.4
  • Python: 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)]
  • setuptools: 0.6c9
  • SQLite: 3.5.2
  • pysqlite: 2.4.0
  • Genshi: 0.5.1
  • Subversion: 1.5.4 (r33841)
  • jQuery: 1.2.6
[ticket-completion]
acceptance_complete = 
acceptance_complete.label = Acceptance Complete
acceptance_complete.order = 4
acceptance_complete.short_label = Acceptance
qa_complete = 
qa_complete.label = QA Complete
qa_complete.order = 3
qa_complete.short_label = QA
presentation_complete = 
presentation_complete.label = Presentation Completed
presentation_complete.order = 2
presentation_complete.short_label = Presentation
build_complete = 
build_complete.label = Build Completed
build_complete.order = 1
build_complete.short_label = Build

Change History

Have a look at the list of modified files related to this ticket.

follow-up: ↓ 3   Changed 8 years ago by ja11sop

  • test_complete_size changed from undefined to 3
  • doc_complete_size changed from undefined to 1
  • acceptance_complete_size changed from undefined to 0

Thanks for taking the time to raise this issue. In fact we have seen some similar behaviour to this also. There is a fix for what might be a related issue (no ticket raised for it yet) in progress. I'll take a look to see if it will address this also. In the meantime can you tell me what versoion of the patch are you using? 0.11.3 perhaps - I see you are patching against trac 0.11.4.

  Changed 8 years ago by ja11sop

  • acceptance_complete_size changed from 0 to 1

in reply to: ↑ 1   Changed 8 years ago by billyr

Replying to ja11sop:

Thanks for taking the time to raise this issue. In fact we have seen some similar behaviour to this also. There is a fix for what might be a related issue (no ticket raised for it yet) in progress. I'll take a look to see if it will address this also. In the meantime can you tell me what versoion of the patch are you using? 0.11.3 perhaps - I see you are patching against trac 0.11.4.

Thanks for the quick reply... Is there a way to tell which patch I used? I should have taken more notes during the install, I vaguely recall using:  http://svn.agile-trac.org/BRANCH/TRUNK/source/agiletracplugin/0.11/patch-0.11.3/ as it was the closest matching patch to the TRAC version I'm using.

Also, do you welcome feedback and suggestions? e.g. excluding duplicate tickets from roadmap. If so, what's the best way to do this? To elaborate on my first post, my team have begun using TRAC again, with your plugin, and would be interested in contributing.

  Changed 8 years ago by ja11sop

I guess the easiest way to tell what patch you are using is to look into the .svn/entries file under the folder of your checkout. The URL used should be there. In your case 0.11.3 looks like the patch you used. The plan is to move to a unified patch as maintaining different patch versions is very time consuming for little benefit. The problem right now though is that there are a couple of issues against the later patches that need resolved first.

I very much welcome suggestions and feedback and the example you give is a good one! For now the easiest way to do this would be to raise a ticket with your suggestion. I've added a suggestion/feedback ticket type for now. In essence a suggestion could probably be expressed as a user story. So feel free to do that, but I understand that sometimes you might just want to create a quick note about one or more ideas. Recently another user created an  IRC channel for agile-trac. That would also be a place to go to chat about the plugin. This is in its infancy so we haven't provided much of a presence there yet but that should improve over time. Of course that medium is better suited to interactive discussion than collating ideas per se.

  Changed 8 years ago by ja11sop

  • test_complete_date set to 05/17/09

  Changed 8 years ago by ja11sop

  • description modified (diff)

  Changed 8 years ago by ja11sop

  • doc_complete_date set to 05/22/09

  Changed 8 years ago by billyr

hi, thanks and sorry for the delay in replying. I checked and found this in C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\.svn\entries:

 http://svn.agile-trac.org/BRANCH/TRUNK/source/agiletracplugin/0.11/patch-0.11.3/trac

I noticed the list of modified files for this ticket. Should I go ahead and apply this?

Thanks for the reply, I'll add feedback through tickets as you suggested.

  Changed 8 years ago by ja11sop

I believe this should now be fixed can you please verify if it works for you? Many thanks for reporting. I've added some documentation also.

  Changed 8 years ago by ja11sop

I think you would be wise to do an svn update of your patch now. There have been other fixes too, though the main wiki pages has not yet been updated.

  Changed 8 years ago by billyr

Thanks again for the speedy response. I'm only a beginner with trac plugs, python etc, so sorry for the dumb questions. I ran svn update and got these files. My trac instance lives under C:\BuildServer?\Tools\trac. Is there something I need to do now to apply the patch?

C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\ticket\api.py
C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\ticket\model.py
C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\ticket\templates\roadmap.html
C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\ticket\templates\ticket.html
C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\timeline\web_ui.py
C:\Python25\Lib\site-packages\Trac-0.11.4-py2.5.egg\trac\web\chrome.py

Also, does the order of the stages in [ticket-completion] matter (I pasted our current config above which has them listed in descending order)?

  Changed 8 years ago by ja11sop

Yes, that looks fine, basically the list is telling you which files were updated to a newer version. Now you need to restart your server, whether that is tracd or Apache depends on how you have set up your trac installation. Once you've restarted you are basically good to go. You do not need to do anything else. If you have an open page in your browser you will of course need to refresh it to see any changes.

As for the ordering of the stages it actually makes no difference. I think by default though trac itself will reorder them into alphabetical order. It just so happens that for the default completion stages this turns out to be in descending order.

  Changed 8 years ago by billyr

Hi again, thanks I re-read AgileTracPluginInstall Step 3, and after a restart I've noticed both problems appear to be fixed:

  • the overall size on the road map now shows for tickets that are fully sized
  • tickets that have all completion stages stamped now show up as green on the road map (yay! we finally have some - albeit very small - green sections on our roadmap)

Thanks very much!

  Changed 8 years ago by ja11sop

  • acceptance_complete_date set to 05/23/09
  • status changed from sized to closed
  • resolution set to DONE

Excellent! Thanks again for reporting and continuing to provide feedback!

Note: See TracTickets for help on using tickets.