Unable to Create a Sub-task when Enforcing Epic Links on Issue Creation

[Daniel Windsor]

We decided that Epic Links were not always being added when creating an issue and found this article - https://confluence.atlassian.com/jirakb/how-to-make-epic-link-required-on-jira-software-issue-create-screen-815566675.html which suggested adding Epic Link as a mandatory Field. This has been done and was working well until we came to create a Sub-task. As this uses the same create issue path it looks for and enforces that an Epic Link must be present, however, sub-tasks are not allowed to have Epic Links so a issue cannot be raised.

Is there anyway around this other than creating as a different issue type and then changing to a sub-task?

[Bindu Binesh]

In this case, you can split the workflow for standard issue types and sub-tasks.

1. In JIRA, go to Settings > Issues > Workflows
2. Copy the current workflow
3. (Optional) Rename workflow, eg: Company Product Workflow - Sub-task
4. Then go to Workflows schemes page to edit 'Default: Software Simplified Workflow Scheme'
5. Click on Add workflow > Add existing , then choose the newly copied workflow
6. On "Assign Issue Types" screen, tick only Sub-Task
7. Publish the changes
   Note that the changes would apply to other projects that share the same workflow scheme.

Once the workflow is split, you can apply the steps on the original workflow to set 'Epic Link' as mandatory again.

[hperez@tycoint.com]

I am also looking for an answer to this problem.

[Jeremy M]

Dear Daniel,

Have you thought about using Automation to set Issue Links on certain Issues when they are not set? This way you will not have to edit your JIRA in a way that makes using it difficult.

Friendly Regards,

Jeremy Mooiman