Opened 3 years ago

Last modified 3 years ago

user story #66 (closed: wontfix)

Set sizes more (maybe) properly when normal resolution options (mis-)checked

Test Complete Size: 0 Test Complete Date:
Documentation Complete Size: 0 Documentation Complete Date:
Acceptance Complete Size: 0 Acceptance Complete Date:
Reported by: augustinus Owned by: ja11sop
Milestone: Undecided Component: workflow
Version: Keywords:
Cc: Blocked By:
Patch SVN Revision: Patch Trac Version:
Blocking:
In Iterations: None

Description

Some of our staffs are used to check "resolve as..." rather than the new "progress..." box, which leads to all sizes reset as zero. It's fine when the resolution is invalid/wontfix/worksforme/duplicate, but not good for just "fixed."

Shall I just re-configure the workflow to eliminate "resolve as..." or could you patch it to set progresses completed at that moment by default?

Thank you!

Change History

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

Changed 3 years ago by augustinus

Hum, I guess this is related to #48.

Changed 3 years ago by ja11sop

Actually it is more directly related to #47. Basically the problem is that with sizing we want to capture when a stage is complete and mark the ticket done (closed) when all completion stages are completed. This is really a replacement for fixed. One thought I had was to remove fixed automatically from the resolutions when installing agile-trac but I am now thinking this is really a documentation issue. In other words when using the plugin you have two ways to resolve an issue. The first is by actually sizing it and then completing it. Once all stages are complete the ticket is now closed automatically. The other alternative is to ignore sizing (such as with duplicates etc.). Therefore only those resolutions that do not require sizing should be maintained.

The easiest option to help mitigate the problem you are having would be to remove fixed as an option. Ideally it would be nice to have the ability to mark a ticket progressed (or even done or fixed) and have the completion stage dates filled in automatically with the current date. That is a little complex though as I'd need to augment each resolution with a marker indicating if it should have that behaviour or not. It could perhaps be a configuration option so that you mark fixed to mean "complete all stages with today's date and close".

The current behaviour was chosen as the first step because it was the least complex to implement while still allowing for the common use-case of back-dating when things are done. It is sometimes the case that a ticket gets updated with it's status after it was completed. It was important not to preclude that behaviour.

I hope my answer has shed more light on this for you. If you are happy with removing the fixed resolution (and hence forcing use of progressed to complete issues, then please mark this issue as worksforme. I'll put a reference to this issue in #47 so our discussion doesn't get lost.

Thanks

Changed 3 years ago by augustinus

It's good enough to me to remove the fixed resolution :)

(But certainly I don't have permission here to mark this issue as worksforme :p)

Changed 3 years ago by ja11sop

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

Of course ;-) I'll set it to wontfix for now unless you have an objection to that. Thanks for taking the time to raise the issue.

Note: See TracTickets for help on using tickets.