You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
Two Request Types share the same Issue Type and the same Workflow.
Logic to apply:
I have already check if atlassian-addons-project-access has the correct permission and it has and it is in place
Eager to hear any opinion . . . and no Add-On or Plug-In solution please
P.S.: this is part of a large automation which I want to keep it small and manageable
Hello @Mario Coluzzi
Are you sure this is for Jira Work Management? I normally associate Request Types with Jira Service Management.
Is this team-managed or company-managed? If it were company-managed, I'd set up Workflow Conditions that would show or hide the transitions based on the request type. This may mean you have to have a transition bypassing the approval.
Can you share a screenshot of your workflow?
Yes it is Jira Service Management the purpose is to build a quite complex authorization and some requests do not require a Line Manager approval.
Interested in hear more on "show or hide the transitions based on the request type". Can you point me to a documentation? I believe this will address my question.
P.S.: I did attach a screenshot of the issue and the -easy- steps I put in place
This could be a simple Value Field condition that you put on relevant transitions
OK, looking at your automation I wonder if it's executed by the Automation for Jira user. If it is, is that user one of your defined approvers (I'm guessing you're using the out-of-the-box approval process in JSM)?