How can we auto assign an issue basis some field value.
For e.g. We are capturing information like Modules & sub-modules on which development needs to be done. Post approval from a team, we want to auto assign this issue basis module and sub-module information captured during create issue stage to a particular person.
From a costing point of view, I would like to highlight that Jira Automation is inbuilt and is available for you to use without any additional charges. Your requirement can easily be implemented via an automation rule. What more is that it requires minimal to nil coding and an easy-to-understand interface. Do explore automation thoroughly before going for any of the external plug-ins that are chargeable.
Cheers,
Bhanu :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mayur,
Glad to be of help.
If you are using Cascading list for modules and submodules you can make use of the JQL condition to check the value and do the needed actions later.
Trigger - Issue created /module-submodule edited etc
Condition - If/Else block
Within If block - JQL Condition
JQL can be written like this:
"<your field name>[Select List (cascading)]" = <first option> and "<your field name>[Select List (cascading)]" = <second option>
Action- Under the If condition, you can add an action component and assign the issue per need.
Just giving a heads-up because I have implemented something similar :)
Regards,
Bhanu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can either use Jira Automation or a workflow post function to achieve this. Are you using any 3rd party app like JMWE, JSU, JWT or Scriptrunner?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the response.
I've heard about Scriptrunner but can you give some more insights on JMWE, JSU and JWT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mayur Gaikwad_Tech PMO I think that you should discover their capabilities by yourself, because this is the way to understand what will suit your needs. They all more or less do the same thing. I honestly like more JMWE since it gives you workflow properties outside of the box, plus the ability to write script using jira expressions, or nunjucks, plus it comes with listeners and shared actions.
But I suggest that you try them all. They all come with evaluation period:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mayur Gaikwad_Tech PMO if my answer helped you, kindly mark it as accepted in order to help others in the community with similar questions. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Mayur Gaikwad_Tech PMO and thank you @Alex Koxaras _Relational_ for mentioning us!
I am part of the support for JWT for Jira Cloud and I bring good news.
You could achieve this with the post function Update fields in combination with the parser function getMatchingValue().
After selecting the assignee field as field to be updated, you could write an expression like the following one to choose a different user depending on the selected option in a custom field.
%{getMatchingValue(%{issue.cf10048}, ["Option 01", "Option 02", "Option 03", "Option 04"], [%{issue.cf10047}, %{system.currentUser}, %{issue.project.lead}, "64gha11hgf231rt55as12uuy"])}
As you might infer from this expression, you can select dynamic values for the assignee field depending on the selected option of a custom field, such as an user from a User Picker custom field, the current user, the project lead or a specific user (user ID).
There is also a possibility to apply a conditional execution, so that the post function will only be executed and the issue assigned when a condition is met. This could be used, for instance, to execute it only if the assignee has not been set.
If you need more information on how to implement this, you can always take a look at our use cases in our documentation, such as Assign important issues to the project lead or Assign an issue to the project lead, if the issue is unassigned on creation, or contact us directly via our Support Service Desk.
Best regards,
Vicente
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.