You can create/move Sub-Tasks only for stories within same project. It is a shame, because it would be helpful to have different projects within a story sometimes. Thank you everyone for your input! @Jack Brickey I am wanting to move an existing task, to a sub-task within a story. To perform an issue action (looped transition): If you only have one action, select the name of the action at the top of the issue. Select Actions at the top of the issue. Select the action to perform. You can perform this action with your keyboard via Jira’s command palette. Use command + K (for Mac) or Ctrl + K (for Windows) to open the In order to select another customer as the reporter of an issue, there are two settings that need to be checked. The first one is the “Browse users and groups” global permissions. Please, go to Cog icon > System > Global permissions and check if the groups you are part of have this permission. Then, go to the Project settings > Customer The scheme is used by a lot of projects, but the change does not affect other agile projects negatively. Try to open the issue type screen scheme, choose a screen for the BUG and try to add the Epic Link field. Maybe I did not understood correctly, but epic Link belongs to issue type epic only. You can create a bug as Issue in epic, then it Upcoming changes: 'epic-link' replaced with 'parent'. Currently, the epic-link connects issues from the base level (containing stories, bugs, tasks) to epics, and the parent-link connects epics to issues at higher levels for those who have Jira Software Cloud Premium. From October 2023, we'll be moving towards a single way of representing You can remove the epic from the issue by: 1. clicking on the epic field that you are pointing to in your question to edit it (note: don't click on the coloured epic lozenge itself, but the field around it as shown in the screenshot below when you hover over the field with your mouse) 2. Back space to remove the text. We use Jira Datacenter v7.6.9 (about to upgrade to 8) and I'm interested in automating repetitive tasks as much as possible. My team is using Kanban, no sprints/scrum, and all issues are in a single project. We're using Initiatives, and each of the (small-p) projects we undertake, will involve pretty much the same boilerplate epics & stories. If a Jira Admin user removes the options available for this field and for the Epic issue type, it will no longer be possible to mark Epics as Done from the boards. Resolution. To fix the issue, we need to add back the default options to the Epic Status field, by following the steps below: Log in as a Jira Administrator user U4Pq.

jira change epic to task