I linked to an existing Epic that has one story and a number of sub-tasks, it is not showing/counting the Done subtasks at all. It is only showing 1 Story in progress. Do I need to edit a settings someone to account for subtasks in the delivery area?
Hello,
Can you send more details or a print of the epic with the issues? This would help us answer your problem.
Hopefully this helps? If I don't link to the Epic, but directly to the story it reports it correctly. I guess my other question is, I have a lot of other epics but don't know if it is counting/reporting all the subtasks that show under those stories as well.
When I point it to the Story and not the epic it reports properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Jeff Maciorowski
The behaviour is expected when you switch between simple and default behaviour. You can learn more about them here: https://support.atlassian.com/jira-product-discovery/docs/configure-the-delivery-progress-field/
In your case, I guess the second display is the preferred option.
Best Regards,
Hermance
Product Manager @ Jira Product Discovery
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hermance NDoungaI am not sure why we are talking about the simple and default behavior. I have not touched those options. What I am showing is what happens when I point to an Epic over pointing to a Story. I just use the existing delivery option and either point to the Epic or Story and it the Epic does not account for any of the statuses underneath it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry I misread your reply above. i thought you were switching between default and simple options.
So, it's still mentioned in the documentation I linked, but basically, the progress is calculated one level down.
So if you point at the epic it looks only at the status of the story.
If you point at the story, it looks at all your subtaks under it.
So it's still expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess this isn't really adding up for me and it can be reporting incorrectly in our views. This could be A LOT of effort to point to so many stories for a project. Why can't I just point to a project so that it can tell me what the delivery for a project is. If I am pointing to our Epics, then its not calculating the statuses correctly. If new epics or stories are created, then we need to remember to go add them here. The concept of this idea is wonderful, but the execution is only good for singular tasks or stories. It doesn't really work for anything bigger.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you figure out a way to get it to do what you want? (Link a ticket to an Epic, but have the bar fill up based on sub-tasks not stories)
We are trying to get it to do the same thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No this is still broken. They need to find a way to make it work better with Epics. It does not look at the full hierarchy and you can't just point it to a project for it to see what needs to be done. If you have 400 tasks, you need to do each one which is silly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.