I need to keep certain workflow buttons hidden from all users permanently as these buttons(transitions) will be called by an external system using JIRA REST API.
I am having really hard time to find out a concrete way of doing this. I tried to use hide transition from user workflow condition but the condition always fails.
So in the end I had to try Jquery in Announcement banner:
//more such action ids which should be hidden
I tried to use some more additional conditions below this code like when transition is 'assign in jira' then reload the page so that the ready function is executed and buttons hide again but there may be some better way of doing it.
if($("#issue-workflow-transition-submit").html()=="Assign In JIRA")
if someone has any insights or suggestions please help!
With a little more effort and help from a jquery expert i was able to get it working.
I think instead the better solution to prevent users from doing this would be to utilizing workflow conditions. These are built into Jira workflows. In your case, I would recommend creating a group in Jira's user management, specifically to be used by your REST API user(s). Once you assign the Jira user(s) to that group that should be able to make these transition, you can then edit the workflow in use by that project, edit that transition and set a condition of "User in group", and select that group name.
Once you publish this workflow, then the only way a user could see that transition in Jira would be if they were a member of that specific group.
You mentioned that you tried this previously but that the condition is always failing. Can you tell us more about what condition you selected, and how you configured it here?
Thank you for your reply!
Background: JIRA<==>Remedy ticket syncing integration
I considered the option to use workflow conditions and using groups. However, we cannot restrict based on user group because typically any user can create ticket from remedy and then to JIRA via scripted APIs so we have to keep it open to all users.
By adding that property to the workflow and then publishing the workflow, issues in that state that use that workflow will not be able to be edited when in a closed state.
Hi Andy Heinzer,
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