Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to automatically add component and add epic link according to certain text in description Edited

Hi All,

I'm fairly new the to automation within Jira. I have two questions.

  1. If a bug is created in a Jira project and in the description field there is, for example, the text {KIM1} Since KIM1 is already created as a component in the project is it then possible to automatic add KIM1 as a component to the bug and if yes. How is this done most correctly?
  2. The second question is in a similar line of the first question if a Bug has {Area10} in the description text is possible to automatically add an epic link if it matches an epic link there has the name Area10

Appreciate your help. 

1 answer

0 votes

Hi @Kasper Post 

The first rule might look something like this:

  • Trigger: Issue Created
  • Condition: Issue Fields Condition - Issue Type (field) equals (condition) Bug (value)
  • Condition: Issue Fields Condition - Description (field) contains (condition) {KIM1} (value)
  • Action: Edit Issue - choose to set Components to {KIM1}

-----------------------

For the second rule, can I clarify the logic is:

  • If an issue is created/updated with {Area10} in the description then...
  • Locate an Epic with {Area10} in the Epic Name and...
  • Link the issue as a child under this Epic

Can I confirm if this logic is correct? If yes, this would be difficult due to the dynamic nature of the second bullet point (eg. what if two Epics had that name).

A simpler alternative would be to create multiple rules, one per Epic. So similar to the above, the Condition would look for a specific phrase in the Description, then the Action  would set the Epic Link based on a single issue key per rule, rather than trying to dynamically locate text in the "Epic Name".

If you can confirm the logic, I'd be happy to look into what is possible :)

Ste

Hi @Stephen Wright _Elabor8_ 

Thanks for the prompt response.

Your logic is correct. There would only be a very small chance that there will be made identical EPIC since these are predefined and created before the project starts.

Kind Regards

Kasper Post

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,138 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you