Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,005
Community Members
 
Community Events
184
Community Groups

Company Managed Epic and Task Child Dates

Frank
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!
Mar 22, 2023

Hi there

 

Hoping somebody might be able to guide me in the right direction as most of the articles i am finding don't appear to help and community posts i've come across are a few years old.

 

I am experimenting with a company managed scrum project and setting up sample Epics with associated Tasks.  I see that irrespective of the Task start and due dates, the Gantt chart shows their dates as the length of the sprint.  The setting for Child level issue scheduling is enabled.  Is there a way to separate the sprint from the Task dates to better reflect each Task in the Gantt view without using a team managed project and disabling the sprint/backlog features?

 

This article appears to reference "Schedule child issues by dates" but i don't see this option in either company or team managed projects.

https://support.atlassian.com/jira-software-cloud/docs/enable-child-issue-planning-for-kanban-teams-on-the-roadmap/

 

Thanks

2 answers

1 accepted

0 votes
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Hi @Frank and welcome to the community,

If you go on your active sprint board and follow the instructions on the page you are referring to, you will see the above image:

child level issue.png

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

And according to this https://jira.atlassian.com/browse/JSWCLOUD-18668 your child issues will always be seen with the start and end date of the sprint:

Once you expand the epic, you will see the stories/tasks and any existing dependencies. If you have scheduled (with dates) sprints in the backlog, the sprints will be displayed in the header of the roadmap. If the story-level issue start/end date has been assigned to a scheduled sprint, each issue will automatically display on the roadmap in alignment with the sprint dates it is assigned (and not from the start/due date fields, if they are being used).
Example: if a story/task is assigned to "sprint 1" with dates 02/11/22 - 12/11/22, the story/task will be displayed that it will start and end to be delivered in that sprint timeframe.
Given Jira Software is an Agile project management tool, this follows closely with the Scrum framework, where work is scoped to be delivered within the timeframe of a sprint. https://support.atlassian.com/jira-software-cloud/docs/schedule-work-for-scrum-teams-on-your-roadmap/

0 votes
Frank
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!
Mar 23, 2023

Hi @Alex Koxaras _Relational_ and thanks for the detailed response.

That does make sense.  Given this is how it is designed, it appears that in order to see child level dates on the roadmap, the only option is to use the team-managed view then.

I also see that another suggestion that I will monitor that might assist anyone else looking: https://jira.atlassian.com/browse/JSWCLOUD-23411

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events