-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.2.6
-
5
-
Severity 2 - Major
-
1
-
Issue Summary
When a user creates a workflow transition and adds the condition Hide transition from user, JIRA Automation rules which use this transition would not be triggered.
_It is important that the transition is triggered by an automation because they want the issue to be closed if no updates after a while, however they must use a different transition from the one visible to users because the ones visible to users have required fields that prevent the transition from being used. _
Steps to Reproduce.
- Create a JIRA project.
- Edit the workflow reusing the transition that closes the issue, linking it between the first status the issue gets to upon creation (Waiting for Support) and Resolved Status.
- Add a condition to the transition: Hide transition from user
- Publish the Workflow.
- Create a new Automation Rule:
When Issue Created IF Issue Matches: summary ~ 'test' THEN Transition Issue:<Your transition from the first status to Close> - Create an Issue.
Expected
The automation rule would be able to automatically close the ticket.
Actual Behavior
The automation rule would not be able to execute and close the ticket. This I suspect is because the automation rule is being run as a particular user.
- was cloned as
-
-
- Closed
-
- links to
[JSDSERVER-4783] Workflow Condition Breaks JIRA Automation Rule
A working solution is to call a global and hidden transition through REST calls from Automation. The condition 'Hide transition from user' doesn't count for REST calls.
I confirm the workaround is working well as expected and offers a pretty nice solution to my problem.
The identified bug should nevertheless be investigated as long as the 'Hide transition from user' condition is maintained, as it may be a more simple and logical option, or even a needed one in other circumstances?
It used to work for me until December 2016 or January 2017 and a Jira Service Desk release upgrade.
Thanks again for the workaround.
Thanks a lot for this answer! (long awaited and desired 
)
At first attempt, the proposed workaround seems to work fine for me:
-> defined a new reserved Jira user (reporter), group (jira-reporter includes "reporter") and role (Reporters includes "jira-reporters")
-> set appropriate autorisations (eg. grant "user can transition requests" to role "Reporters")
-> set automation default event user to "reporter"
-> set the needed automated rule (Options) to run as default event user (eg. "reporter")
-> set the associated transition with the sole condition "User belongs to the project role : Reporters"
Now, the transition is no more visible by Service Desk agents, nevertheless the wanted hidden transition is run by the appropriate automated rule as user "reporter".
Will confirm the workaround is ok after some more experimentations...
Richard Crampton
added a comment - Workaround:
Instead of using the 'Hide transition from user' condition, consider using the 'User is in project role' condition.
Next make sure the user you run the automation rule as is in this group, and those agents who should not see the transition are not.
Have tended in the past to create a dedicated user to run automation rules as for auditability. Does consume a licence seat, but can set up the users email address to be a task id, then additionally alert this user in other automation rules to send email to the task id.
Richard Crampton
added a comment - Workaround:
Instead of using the 'Hide transition from user' condition, consider using the 'User is in project role' condition.
Next make sure the user you run the automation rule as is in this group, and those agents who should not see the transition are not.
Have tended in the past to create a dedicated user to run automation rules as for auditability. Does consume a licence seat, but can set up the users email address to be a task id, then additionally alert this user in other automation rules to send email to the task id.
I also have this bug on JIRA DeskService.
JIRA Core v7.3.2 (ed. 73013) built on Tue Feb 28 00:00:00 CET 2017
JIRA DeskService v3.3.2
An automation rule based on "added comment" fail to transition issues when the transition has the condition "Hide transition from users". Whether the rule is run by user or by the project role.
On the automation rule "view log" screen, the rule appears with Status = ERROR, and the transition is shown with the failure symbol (red !) for the automated rule full-filled condition.
Hello,
This is affecting my automations too, I need to make some transitions only allowed for the Automation Rule, but the rule only allows triggering if there is no conditions for the users to see it. I tried to only give the permission to the Automation Rules User, but this user is not on the list of Jira Users, so is unelectable.
This is affecting the last version of Jira cloud.