I am new to JIRA and I have 2 questions about Epic estimation and issue links:
Epic estimation: I created an epic, then I created some issues with estimation inside this epic and the epic estimation changed corresponding. When I create some sub-tasks (of above issues) with estimations, the total estimation of issues increase. However, the total estimation of epic does not change.
Did I use JIRA incorrectly?
Thank you in advance.
Let discuss more about issue link. I think an issue link is not fully a relationship. If your call a link is a relationship between 2 specific items, there should be constraint between them. For example, the relationship between issue and sub-task. The issue cannot be closed if its sub-tasks are not closed yet. I think this is the "lock - is locked by" constraint of the relationship. while the issue links don't have the constraints like this.
Why does there need to be a constraint? If an issue has a link to another that says "the issue at the end of this link might tell you something interesting about the current issue", there's no constraint, it's a relationship, shown by a link.
If you need to impose constraints, that's a function of your business logic, not the simple structure of a link. There's nothing wrong with that idea, but Atlassian have not coded for it because that's not what they use links for. They've kept them as simple informational links, not tried to build anything on top of them.
You will need to implement logic to suit your usage and cases. Have a look in the marketplace, there's quite a few add-ons that will use the link information to do things like "you can't progress this issue through the workflow unless all the issues linked to it with <link type> are resolved"
@Nic Brough [Adaptavist]. I'm wondering why my time estimation for an Epic is not related to the time estimates I make for tasks that are part of that epic. Would I be correct in understanding that your #1 response applies to this problem, and that we would not expect this behavior to change?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs