You need to click on the story in the lists of issues in the Backlog screen and you need to drag it over to the Epics pane and drop it on the Epic where you want it added. That should add the story to the Epic without changing the Story's position in the list of issues. At my side - the view does not look like yours.
There is no option there to create or convert subtask. To change a story to a task etc I just click on the icon next to the jira number and click change issue type. For sub task its disabled. Go to your ticket under MORE --> Convert to You can also convert a task to a sub-task the same way.
To make the trigger issue a child of the new epic, you will need to save the epic key and edit the trigger issue after your branch. I bolded the new sections, as shown below. trigger: issue created. action: re-fetch issue. condition: issue type is action: create a new Epic. action: create variable. name: varEpicKey.
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.
The rule needs to be enabled in order to run. There's a little switch that shows green in the top-right corner when a rule is enabled (when viewing the Rule Details). The rule also has to be configured for the Jira Project (s) where these Epics and Story-level issues are located. You should also look in the Audit Log to see if the rule ran, and

You just need to add "Epic Link" to the create issue screen in Jira. Te field have to be available in the UI action so you will be able to do it also from the REST API. Let me know if you still encounter problems after adding the field. Since than i have been trying to find "How to create an epic link but no luck!"

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 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
What we do/have done is: Created a Milestone issue type. Add the relevant milestones to the Epic as part of Planning. Create a view in Advanced roadmaps that only shows the Epics and their milestones. This creates an easy to view Timeline (including which sprint the milestone is expected to occur in) see below. Reply.
Kl04D.
  • f6fgmb0b7q.pages.dev/547
  • f6fgmb0b7q.pages.dev/685
  • f6fgmb0b7q.pages.dev/346
  • f6fgmb0b7q.pages.dev/815
  • f6fgmb0b7q.pages.dev/382
  • f6fgmb0b7q.pages.dev/976
  • f6fgmb0b7q.pages.dev/977
  • f6fgmb0b7q.pages.dev/517
  • f6fgmb0b7q.pages.dev/803
  • f6fgmb0b7q.pages.dev/10
  • f6fgmb0b7q.pages.dev/923
  • f6fgmb0b7q.pages.dev/996
  • f6fgmb0b7q.pages.dev/430
  • f6fgmb0b7q.pages.dev/614
  • f6fgmb0b7q.pages.dev/948

    • jira change epic to task