Hi All,
We have a requirement say, depending on the value of a Custom Field the story should Auto-Transition from one state to other state.
Example:- Assume the story is in Dev Integration Test state, at this point a custom field drop down (QA Integration Test) with Yes / No values is set. If the custom field value is set to Yes the story should auto-transition to QA Integration Test, if No to Move To QA Test state.
Solutions are most welcomed and much appreciated.
Thanks in Advance, venkat
You'll need to write a listener plugin to do this (or use the Script Runner, which allows you to code without having to write a whole new plugin)
I've said to use a listener because that can detect and run on any event you chose to trap. It sounds like you probably want to trap "edit" and then check the status and custom field valures. It's also a nightmare trying to trigger a second transition in a post-function - don't even think about trying that! I've yet to see one work at all.
Thank You Nic for the valuable information
You can also use JJupin for that. Auto-transitioning an issue through the workflow is as easy as writing
autotransition(<transition_name_or_id>, <issueKey>);
You can either run this in a Listener (created with JJupin as well) or directly as a post-function (I see Nic hasn't tried JJupin yet).
HTH
Have a look at this, this is what I implemented,
https://answers.atlassian.com/questions/143150/skip-or-follow-a-transition-step-based-on-cutom-field-value
Hi Florin, I don't have the exact same situation, but similar lines
Whenever an issue is created it has a "Draft" status. the next status it transitions into is "Waiting for approval" and then "approved"
I want the issue to automatically transition from "Draft" to "Approved" if a certain field has a specified value. In this case, the field is Type and value is "Standard".
So if the issue is of the type "Standard" then it should go from "Draft" to "Approved" else it should follow its natural route.
@Nic Brough -Adaptavist- : Is this still the existing solution or do we have something better now?
Currently I implemented a Listener which transitions the ticket when it receives an Update event but realized there's a criticality in Jira's implementation whereby the issue might be in an inconsistent state just after having been updated and the transition fails, the result is that Jira returns an:
"It seems that you have tried to perform a workflow operation (some-transition) that is not valid for the current state of this issue"
Of course the transition is valid instead.
Someone suggested setting the workflow states which are null or 0 to "ACTIVATED" manually through the following code:
List<GenericValue> workflowEntries = ComponentAccessor.getOfBizDelegator().findByAnd("OSWorkflowEntry", FieldMap.build("id", issue.getWorkflowId()))for (GenericValue workflowEntry : workflowEntries){if (workflowEntry.getInteger("state") == null || "0".equals(workflowEntry.getInteger("state").toString())){workflowEntry.set("state", new Integer(WorkflowEntry.ACTIVATED))workflowEntry.store()}}
However this solution doesn't seem to work for me.
It looks like you're new here. Sign in or register to get started.
