Hi,
I want to create some rules in Jira. Wondering how type of parent can be checked for bug or task ? This also requires dynamically setting custom fields to required options based on condition.
Rules required are:
if Bug is not part of an Epic, set CustomBucketField=Corrective Content
If Task is not part of an Epic, set CustomBucketField=Operations
If CustomBucketField=blank, app. assigns per RAB
RAB stands for Resource Allocation Bucket which is another custom field like CustomBucketField.
Hello @Nauman Ahmed
An automation rule structured similar to this may help you. I second @Mark Segall questions and approach, but I'd suggest simplifying the "Epic check" condition as illustrated:
As Mark asked, I am not sure how your last rule above plays into this, if that last rule does not depend on the presence/absence of an Epic, then you would need to restructure the rule as I illustrated it here.
Hope this helps
Hi Samuel,
thanks for your prompt response.
I am looking at your screenshot - are you using any particular plugin ?
This doesn't look like automation for jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Nauman Ahmed this is Automation for Jira, it looks different from what you posted as I can see you're using the server version.
In any case, it looks like the Related Issues condition should work if you want to check the existence of an Epic:
I understand it will look a little different than what you're seeing, but if you have the "Related Issues Condition" then you should be set
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nauman Ahmed - As @Sam Nadarajan suggests this will work on Jira server. I have confirmed in my environment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nauman Ahmed - You'll want to think of it in terms of trigger, condition, and action. From your description, it sounds like you have a condition and action, but I'm not getting how it triggers. So, if you need help with that please, share when this rule is expected to trigger (e.g. issue created, field value changed, schedule, manual, etc.).
It sounds like you have a couple conditions:
Here's how you can address it (this is based upon company-managed so if you have a Team-Managed project, you'll just need to substitute Parent wherever I reference Epic Link):
I'm not entirely sure of the last condition so what I have there is based upon my interpretation of what you shared in the description.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sam Nadarajan / @Mark Segall : guys thanks for pointing me in the correct direction, i've managed to create an automation rule - there is only one issue
The EPIC LINK field is not available for automation rules, it does not show in the list of available values and i learned that it used to be available but then it was removed.
In the picture uploaded - the highlighted field should be EPIC LINK - is there any way to get that in automation rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.