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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

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: http://oswf.sourceforge.net/tutorial/index.html).

I found this as appropriate solution:

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

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

2 comments

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 _Snapbytes_ ,

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")
log.setLevel(Level.DEBUG)

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(afterStep)

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

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.

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you