Best practice #4: use Outlook alerts to your advantage. The last tip is for situations like when you immediately want to be alerted for certain Jira Software events. When using Outlook rules, you can use the action Display a Message in the alert window. This will show a dialog in Outlook, which you’ll need to confirm.
1. Open the subtask, which you want to convert, on a dedicated window (i.e. not from the board). 2. Click "see the old view" in the top right. 3. right-click the '' on the top right and click "convert to subtask". 4. Choose the issue that you want to be the parent issue. 5. Click "next".
Note: You will not be able to convert an issue to a sub-task if the issue has sub-tasks of its own. You first need to convert the issue's sub-tasks to standalone issues; you can then convert them to sub-tasks of another issue if you wish. Sub-tasks cannot be moved directly from one issue to another — you will need to convert them to standard
Answer accepted. Thomas Schlegel. Community Leader. Mar 17, 2017. Hi Gintare, no, an Epic is an issue type and a project is a project. No transformation between them. Create a new project and move all the issues belonging to the epic from the old project to the new one. Reply.
Move an issue from JIRA Service Desk to JIRA Software. We've been big users of Jira Software for a long time now and are starting to look at the Service Desk application, however I have found one blocker in our testing. Right now, our user access to Jira is open for anonymous users, but if you want to contribute to an issue you need a login. Hi all, just wondering how I can trigger in the JIRA project automation: "Convert Sub-task to Issue". in the way, that a Sub-task is converted to a. Task or a Stroy. and if so, to keep the current sprint value. Though about Field changes. But how to create a rule with. Type was "Sub-Task" and is now "Task" OR "Story". .
  • 38ricmvnc5.pages.dev/390
  • 38ricmvnc5.pages.dev/270
  • 38ricmvnc5.pages.dev/283
  • 38ricmvnc5.pages.dev/293
  • 38ricmvnc5.pages.dev/50
  • 38ricmvnc5.pages.dev/366
  • 38ricmvnc5.pages.dev/138
  • 38ricmvnc5.pages.dev/418

    • jira convert task to bug