Hello @Julina Del Rosario
Can you show us the diagram for the workflow you are using where "Epic" is a status? "Epic" is typically a work item (a.k.a. "issue) type rather than a status for a work item.
Or are you talking about changing the type of the work item from something else, like Task, to Epic?
If you have only native functionality available to you it is not possible to set up a requirement that during a status change a user is required to link the issue to an issue in another specific project. That would require addition of third party apps that extend the capabilities of workflow customization, such as ScriptRunner or the ones listed here:
https://marketplace.atlassian.com/search?query=jira%20workflows
Do you have any such apps available to you? Is your company open to getting any such apps?
Possible work-arounds without apps:
1. Use an Automation Rule to review the work item after the status change was completed. An Automation Rule could be used to determine if the work item has a link to an item in the specified JSM project. If no such link exists, then the Automation Rule could change the work item back to a pre-Epic status.
2. You could alternately create a custom field that indicates by count or by Yes/No if the work item has been linked to an item in the JSM project. You could use Automation Rules to monitor when items are linked to the work item, and update the custom field accordingly. You could then customize your workflow transition with a Condition that checks the value in that custom field, and allows the transition to complete only when that custom field indicates a link exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.