Community
Q&A
Jira
Questions
Automatically assigning the assignee as per epic name

Automatically assigning the assignee as per epic name

Hi folks

I have 5 teams i am creating epics having child tasks . i am looking for automation if i select Hardware it assign to user1 ,Embedded it assign to user2

2 answers

0 votes

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hi @SandeepSingh R

That seems possible to implement with an automation rule. And...

Using automation requires learning and experimentation. I encourage you to try to create the rule, and if you run into challenges, post images of your rule and the audit log details, describe what is not working as you expect, and the community can help.

To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This is how i tried to do

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Bill Sheboy likes this

Thanks for the reply

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Is your rule working as you expected?

It does seem to have a problem: the issue type for Epic is only tested once. Please consider separating that as a basic condition, and move it immediately after the trigger. Then the if/else tests will not need it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

No its not working, can you suggest the flow or write it for the reference, so that i can build further

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Please describe how it is not working as you expect.

To provide more context, please post an image of the audit log details showing the rule execution when it does not work as you expect.

And did you see my comment about the condition test on Issue Type is epic? As that is only in the first condition, it is possible non-epics would be selected for the later conditions (i.e., the else/if conditions)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Should i select for all issue types

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

As you wanted to do this for epics, I was suggesting to perform the issue type test first, and then the others.

For example:

trigger...
condition: issue type is Epic
if/else condition for epic name equals Initialize
- assign as needed
else/if condition for epic name equals Hardware
- assign as needed
and so forth...

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

sorry didnt get you can you send snapshot

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Would you please post an image of your current version of the rule? I suspect one or more of your actions is an incorrect type now.

And...if possible try to post the entire rule in one image; that will help confirm the rule matches what you are posting. You can capture the entire rule either using a browser addon for scrolling image capture or a separate screen capture application.