The default duration of issues depends on the timeframe setting on your timeline. If your timeline is set to: Weeks - your issues will be 7 days long. Months - your issues will be 14 days long. Quarters - your issues will be 30 days long. Drag either end of the schedule bar to change the start or end date. Alternatively, you can right-click on
For hierarchical and other reasons we want Epic --> Issue (Task, Story, Bug) --> Sub-Task. Unfortunetly new people always create Sub-tasks under an Epic, so I am looking for a way to block thar or even remove sub-tasks under Epic.You can create a manually triggered Automation Rule to do this in Jira -. Branch rule for all issues in Epic - clone and update summary to be something like "Clone - { {triggerIssue.summary}}" Clone Epic to new Epic, linking to trigger issue. Branch rule for all issues in epic. * if summary starts with "Clone -".Try this first: Project settings -> Summary -> Issue types and check what issue types do you have in your project. If you do not see that, click on the scheme to go to the mentioned issue type scheme and then add Story there. Do not create a new issue type called Story as by default Jira Software comes with Epic, Task, Story, Bug issue types. 2. Added the "insert JQL Query, issuetype = feature" function. 3. Added the "insert JQL Query, issuetype = epic" function. This would result in showing the Epic and having a "break" between the Epic and Feature level. The feature level now shows stories linked to it and no duplicated stories were added. VBvO.