Hi Team,
As we cannot display or get the value of the linked issue from the customer port, I have created a text field where customers can provide a linked issue key and using automation link the issue. But further, I want to have a condition where issues must not link if the linked issue status is in closed status. We have the JMWE plugin but are unable to figure out the solution.
Thank you
You can use a BRANCH for JQL and inside the BRANCH put the following:
FOR JQL: KEY = {{issue.customfield_XXXX}}
Replace XXXX with the ID of the field where the user enters the key of the item to be associated.
Inside the BRANCH put a condition to check the status of the issue and only after that condition, put the action to associate with the current item.
Let me know if you have doubts.
Hi @Fernando Eugênio da Silva ,
Thanks a lot for suggestion. Following automation worked.
To take this more advance, I want to add an error on create screen if the issue key provided is closed or canceled. Is it possible or any workaround?
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Siddesh Mahajan , glad to hear that worked!
An error on the creation screen considering the field issue key statuses would not be possible.
What you can do is create a second BRANCH with the same JQL with the opposite condition: If the STATUS is EQUALS: CLOSED, DONE, ETC
Then: Add a comment
In the comment add a response for the user saying that the issue filled on the field is closed.
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.