[#JRA-9554] Create custom workflow elements to action specific transition based on specific field value

JIRA

Create custom workflow elements to action specific transition based on specific field value

Created: 05/Mar/06 04:25 AM Updated: 24/Apr/08 04:06 AM

Component/s:

Custom Fields, Custom Fields (new types), Workflow

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-9553 Allow specific users to be notified based on specific field values

Participants:	Anton Mazkovoi [Atlassian], Benjamin Naftzger [Atlassian] and Jess Shihady
Since last comment:	24 weeks, 5 days ago
Labels:

Description

« Hide

A custom has requested the ability to allow workflow paths to be based on specific field values.

This would be made possible based on:

1) issue creation where specific field values would dictate the initial workflow status the issue was placed in upon creation; and
2) field value specified during workflow transition screen.

So depending on the field values the issue would move to the appropriate workflow status as configured by the user in a custom workflow.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 05/Mar/06 05:27 PM - edited

This should be possible by writing a custom listener.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 05/Mar/06 05:29 PM

Making this fit all situation would be difficult, and making a configurable listener might confuse the users. Maybe the best way to deal with this is to write up skeleton code that the customers can then massage to their needs. The code can be available via the JIRA Extensions space in Confluence.

[ Permlink | « Hide ]

Jess Shihady added a comment - 23/Apr/08 12:20 PM

I think this is similar to an issue I have. I have been requested to modify our workflows as follows: if more than one value is selected in a given field (probably a custom field), then a different workflow path is selected versus if there were only one value selected.

Specifically, if a bug affects more than one Configuration Item (CI), then it must pass through two separate levels of testing (designated as two different steps in the workflow), but if there is only one CI affected, then the issue only needs to pass through one level of testing.

I don't know much about the listeners, so I will look into that, but this is definitely a feature I'm interested in.