Automation failure for Issue Type

[Michael Lombardi]

I have an automation built in to do 2 things when the Summary contains specific characters:

• add a specific label
• transition to a new status

The first is always successful when expected. The second fails with the error message: "Error transitioning issues BOPSTRAD-1977 (The issue type selected is invalid. (issuetype))"

I have not set any if statement regarding an issue type, all it does it compares two values, as described above, so I'm struggling to figure out why it is failing.

Any help would be greatly appreciated!
Thanks,
Michael

[Brant Schroeder]

An issue type is associated with a specific workflow.  Look at the issue that failed and then at the associated workflow.  Does the workflow contain the status you are trying to transition to?  If it does can it transition from the status it is in to the status you are trying to move it to? (Is there a transition connecting the two statuses)

[Michael Lombardi]

[Michael Lombardi]

Looks to me like there are no issues with the workflow. The automatic prompt is from "TO DO" to "WEB TRADES"

[Michael Lombardi]

[Brant Schroeder]

I think that the issue is that there is no transition from created to Web Trades.  You will want to either create a transition from create to Web Trades or change it to check when the status is To Do and the summary contains.... transition to web trades.  Let me know if that works.

[Michael Lombardi]

Unfortunately it wouldn't allow me to add a transition from Create at all, so couldn't go that route, however I took the other piece of advice and simply checked the status from To Do and it worked! Thanks so much for your help @Brant Schroeder !

[Michael Lombardi]

@Brant Schroeder really weird, the test I did worked, and then the next issue that came through on its own failed on the final step. So the new Comparison works.

Any ideas?

[Brant Schroeder]

Would need to know more about the automation.  Is it still running on created?  

[Michael Lombardi]

It is, yes, but it is passing the compare condition that asks if it is in a specific status, so I'm not sure how that would affect this?

Also, JIRA doesn't seem to allow a transition to begin from before the first status (it is not an option when creating a new transition in the workflow).

[Brant Schroeder]

Michael,

  The transition it is looking at is still from create to to do.  I believe this puts us back where we started.  I would suggest that you add an automation that looks at issue transitioned as the trigger and add a condition of status equals to do and summary contains "....". I think you will get the desired result.

[Michael Lombardi]

It doesn't seem to recognize a new ticket that falls into To Do as a "transitioned" issue

[Brant Schroeder]

I was able to create the following automation in our test environment and it runs just fine.

• Issue Created
• Issue Matches: summary ~ "Testing" AND project = "project name"
• Transition Issue: In Progress (891) -> Project Name: Service Request Fulfillment

This runs fine.  I then changed the transition to a transition that is not in the workflow and got the error that you are receiving.  My guess is that you have multiple workflows in the project or you are using a workflow outside of the project.  This is the reason it can not transition.  You will need to be more specific with you JQL and specify the issue type as well to ensure it uses the proper work flow.  You may have to add several conditions if this spans multiple workflows.