Only let a user's manager run transition

[Franz Maruna]

We've got a shared workflow that is really nice for our organization. 

What we'd like to do is keep the process of making and flushing out tickets as open ended as possible (anyone can do it) and even give them the ability to assign it to a specific person (sometimes problems are just clearly for person X to solve). 

At a specific step in the workflow (moving it from into "to-do") we want to limit that to ONLY the assignee's manager. That person may not be the requester. 

We have several different department groups and a management group... 

Is there any way to achieve this in Jira cloud?

[Brant Schroeder]

You can add a condition on the transition that would prevent certain groups or other requirements to be met in order to transition the issue.   You can learn more here: https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html 

For more advance conditions you should look at JSU or ScriptRunner.  These plugins allow for additional more complex conditions to be implemented.  You will also need a way to determine who the specific persona manager is or you will not be able to build the logic.

[Franz Maruna]

yeah i know about conditions, was just looking for the second half of this... 

1) how to best configure who someone's direct manager is.. I'm guessing setup a custom field on the user record instead of trying to use groups?

2) how to add some code to a condition... basically:

If (user.manager=active.user) { allow_next_step; }

[Brant Schroeder]

As an admin you can add a user property that can contain this.  https://confluence.atlassian.com/cloud/update-roles-and-properties-for-jira-users-744721647.html  You will then need to use a plugin such as ScriptRunner to write the condition.

[Kristian Walker _Adaptavist_]

Hi Franz,

Thank you for your question.

I can confirm that it will not be possible to achieve this requirement with ScriptRunner for Jira Cloud, due to the fact that the plugin is unable to provide the same workflow conditions functionality that the server version provides.

The reason we are unable to provide this functionality is due to the restricted functionality and API's which Atlassian provide inside JIRA Cloud, due to the fact that Atlassian only provides a Rest API in Jira Cloud and not the same Java API that the server version contains.

You can see more detailed information on the differences between ScriptRunner for JIRA Cloud and ScriptRunner for JIRA Server inside of the documentation page located here.

Regards,

Kristian

[Denise_Wuethrich_beecom_products]

JSU can certainly address your concern. It configures workflows without coding and has an easy-to-use interface that eliminates tedious coding and time-consuming testing, debugging, and error-fixing. You could find out more on this link:  https://confluence-apps.beecom.ch/display/JSU/JSU+Configuration+Guide