Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Epic Link Required via Workflow Create Action, but is not being respect on "Move"

Jeffrey Bistrong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 8, 2023

In jira software, you are unable to set the epic link (or parent) field as a required field through the field configuration. 

However, I was able to work around this by adding a condition to the Create action on the workflow to make the epic link required. 

However, it does not work when issues are moved from one project to another. Are there any other solutions out there we can explore to ensure the epic is required when issues are moved into X project.

Monosnap Transition_ Create Issue - JIRA 2023-11-08 13-23-27.png

1 answer

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 7, 2018

Hello John,

Per your description, you would like to display in a swimlane all the issues in your project that are linked to issues in another project. Is that correct?

If that's the case, you will need a plugin to return this information. The Script Runner plugin give you some a JQL parameter that provides you this kind of information: linkedIssuesOf

issueFunction in linkedIssuesOf("project != testproject")

For more details about it, you can check Script Runner documentation in the link below:

Scripted JQL Functions

Please, let me know if it works for you.

J.M.
Contributor
November 12, 2018

Thanks for the response. Would be great if I didn't need a plugin

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events