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?
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.
In this case, you can split the workflow for standard issue types and sub-tasks.
Once the workflow is split, you can apply the steps on the original workflow to set 'Epic Link' as mandatory again.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs