Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When transitioning an issue, how can you get the target status

I faced the same issue as described in

Unfortunately, solutions based on OSWf objects didn't work for me (btw: I found valuable go through its concepts:

I found this as appropriate solution:

final String newStatusId = ComponentAccessor.workflowManager.getNextStatusIdForAction(issue , transientVars['actionId'] as int)

Comments to the code:

  1. issue status is set only; there is NO "ComponentAccessor.issueManager.updateIssue(" and I don't think it would be a good idea to do that
  2. ConstantsManager can be used to get status if you don't need to set it in issue


Tuncay Senturk Community Leader Nov 13, 2019

Hi @Hubert Sękowski 

Why this solution didn't work for you. What was the problem? As you can see that was my post and it worked for me well. The place of the post function is also important to get the destination status.

Hi @Tuncay Senturk ,

Not sure "why" your solution was not working for me.

The most important it does not give expected value.

Below a code snippet, so you can compare your and my solution as well as a given result:


import org.apache.log4j.Level
import org.apache.log4j.Logger
def log = Logger.getLogger("moveParentFromSubApproval.groovy")

import com.atlassian.jira.component.ComponentAccessor
import com.opensymphony.workflow.spi.SimpleStep
import com.opensymphony.workflow.loader.ActionDescriptor

List currentSteps = (ArrayList)transientVars.get("currentSteps");
SimpleStep simpleStep = currentSteps.get(0);
int actionId = simpleStep.getActionId();
int beforeStepId = simpleStep.getStepId();
def workflow = ComponentAccessor.workflowManager.getWorkflow(issue)
ActionDescriptor ad = workflow.getDescriptor().getAction(actionId);
int afterStep = ad.getUnconditionalResult().getStep();

log.debug( ComponentAccessor.workflowManager.getNextStatusIdForAction(issue , transientVars['actionId'] as int) )


Here is the output:

2019-11-14 04:02:41,019 DEBUG [moveParentFromSubApproval.groovy]: 2
2019-11-14 04:02:41,019 DEBUG [moveParentFromSubApproval.groovy]: 11601

BTW: 11601 status category is not 2, that was my first idea when I saw that

Tuncay Senturk Community Leader Nov 14, 2019

As I mentioned before the order of the posy function also matters.

If it is down below the database persist, then it gives different results.


Log in or Sign up to comment