Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to show tasks, and subtask in epic on the timeline display.

Ivan Landerson das Chagas Pinheiro
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 27, 2023

I recently created a personal task manager template. Created a epic, a task added to this epic, and a child of this task. When i open the timeline of the project, the tasks linked to the epic don't show below the epic. Like the epic and task are not related. How can i solve this?

2 answers

1 accepted

0 votes
Answer accepted
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 29, 2018

Hello,

In the issue type scheme you should add a standard issue type. Just add it.

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 29, 2018

You should first create two screen schemes: one for standard issue types and one for subtasks. Then you should associate each screen scheme with an issue type in the issue type screen scheme and then associate the issue type screen scheme to your project.

0 votes
Deleted user
October 29, 2018

Thank you, Alexey.  I understand that it wanted an issue type (and I thought sub-task WAS a standard issue type).

I've since ascertained that the issue type scheme corresponds to the entire project, which implies that I can have different screen schemes associated to either the task or sub-task.  However, the screen scheme seems to only allow one or the other, not one for each issue type.

The workflow seems to be fine; it allows the sub-task workflow for only the sub-task screen.  Trying to figure this out through trial and error is a frustrating process, especially when most "beginner" documentation is geared towards agile projects, not business projects.

I'll keep plugging away, but if anyone has gone through this successfully, I would love any tips!

Deleted user
October 30, 2018

I discovered that although the association of the issue type screen scheme appeared to be an either/or scenario, it was actually accepting both schemes.  My frustration was that I was following directions meticulously, but it appeared that only one scheme was active when both were.

Thank you again Alexey.  I will be glad when we upgrade to the latest version of Jira.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events