Jira Software Cloud - Can I automate a component value based on input value of a custom field?

[Gail]

This is a bit painful.   

We have a custom field (Requestor Team) that is a user-selected single value dropdown.   We want to select a component value based on the custom field value i.e. requestor team = Finance then we want the component value Finance added.   

We need component populated to be able to report properly in roadmaps as you can't use a custom field for rollup.

How would I create an automation rule for this one?

[Mike Rathwell · Accepted solution]

Hi @Gail 

Nope... not painful and I am gratified to see another weirdo like me that uses Jira outside the traditional techdev realm.

I don't have the exact incantation in front of me but the framework is:

• Trigger on "Requestor Team" value changing.
  • This covers both create and subsequent changes to that field
• Lots of conditionals under that to the effect of
  • If Requestor field == Finance set field Component/s == Finance
  • If Requestor field == some other set field Component/s == some other

[Gail]

Awesome!    The only caveat would be..... the field is set by the user in the JSM portal when they create a ticket (fill out a form) so I think the rule needs to be there.??   

Something like this?

[Gail]

Have you ever seen a rule have a "cut off" limit of displaying values for a field?   My custom field has 19 values, but in the conditions for that field it will only show 14.    Hope this isn't a bug I need to report.

[Mike Rathwell]

You might need to have two rules; one for create and one for field changed. I would try with the rule you showed there and test. The hole I can see is the async nature where the field is filled but there isn't an actual issue yet to trigger the change event.

I had not seen that issue with too many rows but I've not stumbled across it myself. I do find that I use both Automation and also Jira Misc Workflow Extensions which has most of the Automation capabilities in it but is sometimes more selective and easier to condition. Both are things I use in my day to day with JMWE especially being a relied on swiss army knife.

[Gail]

Thanks @Mike Rathwell  I tested the rule above twice, and it failed both times.   I have the trigger as field value changed when creating an issue (see below).  

The rule is in my JSM project as flow is USER GOES TO PORTAL AND CREATES NEW REQUEST USING FORM --> IN FORM THEY SELECT DROPDOWN VALUE FOR REQUESTOR TEAM --> ONCE SUBMITTED JSM ISSUE COPTREQ-## CREATED.

The issue in JSM is then used to create a linked issue in a Jira Software project BUT.... the requestor team and component values are not touched so I felt there would not be anything to use for a trigger unless it was the linked issue creation itself