Feature #6220: Named action on ticket status change. - Redmine

Actions

Copy link

Feature #6220

open

Named action on ticket status change.

Added by Joël Lamotte about 14 years ago. Updated over 12 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Issues

Target version:

Start date:

2010-08-26

Due date:

% Done:

Estimated time:

Resolution:

Description

Currently, changing ticket status is achieved by selecting another status in the ticket edition form.

That way don't help to realize that by changing the status we actually performed an important action in the issue's life. For example, if you have a bug issue in "need_validation" state (that says that the issue is fixed but it requires tests from the testers/QA ) and you want to pass it to "fixed", you might not figure that you're actually "validating" the fix and closing the ticket.

It's convenient to see those kind of actions as "actions to perform" instead of side effect of issue status change.

TRAC solves problem this by providing ways to name (via a sentence) each change between two states of a ticket. It then generate an action choice box that is more clear about what you're actually going to do with this ticket.

I've added 3 screenshots of some tickets in my own TRAC (with an old project that I'd like to migrate to RedMine later) to illustrate the idea.

Now it's not a perfect solution : making links or buttons would have been even more explicit I think.

Anyway, it would be far more useful for RedMine to allow for naming actions on tickets.

Files

Download all files

trac_actions_klaim.png (11.2 KB) trac_actions_klaim.png	a ticket "to_see"	Joël Lamotte, 2010-08-26 01:26
trac_actions_2_klaim.png (3.45 KB) trac_actions_2_klaim.png	a closed ticket	Joël Lamotte, 2010-08-26 01:26
trac_actions_3_klaim.png (6.9 KB) trac_actions_3_klaim.png	a new ticket	Joël Lamotte, 2010-08-26 01:26

Related issues

Actions

Copy link

Updated by Eric Davis about 14 years ago

Category set to Issues

This would be nice. It could get difficult due to how many different states and workflows that are allowed on an issue though (and since workflows can be different based on Roles).

If someone wants to create a plugin to prototype this, I'd be happy to review it.

Actions

Copy link

Updated by Joël Lamotte about 14 years ago

Eric Davis wrote:

This would be nice. It could get difficult due to how many different states and workflows that are allowed on an issue though (and since workflows can be different based on Roles).

That would be totally optional, allowing to setup this feature on specific state transitions.

Actions

Copy link

Updated by inS klakier over 13 years ago

This is definitely something I miss in Redmine. Not only Trac has workflow actions - JIRA also implements them and does it in a nice way - as hyperlinks on the side bar, just below the issue details. It is very intuitive to update issues using actions (if configured and named properly).

Trac's implementation has a very nice detail - action not only changes status but can be configured to change assignment or do some other useful stuff. For example, action "accept" (created by default) changes status from any active to "accepted" and assigns the issue to the person who is logged in :)

But Redmine is so much better than Trac...

Actions

Copy link

Updated by Tom DeMay over 13 years ago

what about this... would this be easier? To have e-mail notifications setup on queries, so when the result of the query changes and e-mail is sent? That would provide more flexibility and probably and easier user experience. That's of course if there is a way to do it without creating a performance problem continually validating queries on every update. To address the performance problem you would only validate queries that have subscribers, but in the UI warn of potential performance issues of adding subscribers to queries.

Actions

Copy link