No, in most cases, they should not do this. Why should due-date on issue X change just because it happens to be linked to another issue that changes? I know what you're thinking of - project planning where you want *dependencies* to change if dates move. That's fine, but it's a disaster to do it at issue level automatically. If you really need this, please don't try to inflict it on issues. Planning dependencies is a totally different thing. Have a look at the Portfolio addon instead - that does planning without needing to break all your issue data.
I am confused. JIRA is supposed to be able to do Project Management. If I use MS Project for managing a project, I can set it up, so that the start date of one activity is dependent on a previous activity. If that is not possible in JIRA / JIRA Agile, then not sure, how it can be called a Project Management tool and not have a way to do such basic things that other PM tools provide out of the box. If there is any blog articles that explain how to setup dependencies to handle such scenarios, please advice
Date planning is NOT project management, it's one *tiny* part of it. I'd also point out that a desired due date should NOT move because of dependencies, that breaks the whole point of having a due date - you should be planning on release dates. The really simple scenario here that proves due dates should not be used like that: "The company needs to plan for Christmas". You enter a due date of 25th December. You should not, and can not change the due date. You can plan to miss it completely, but changing it is nonsense. It doesn't matter what your dependencies or resources are, it's still due on the 25th. You need a set of planned dates to be set up and/or use the release dates on versions. In fact, dependency and resource management can be quite a complex field in itself, and JIRA is only part of the toolset you could use. Personally, I never describe JIRA as "Project management" software, because it only covers the "task list" and "issue tracker" part of project management. In some ways, I think Atlassian picked the wrong phrase for describing JIRA in that sense. Jira handles that planning well in an Agile sense, but not the overall picture (for that, I'd reach for Portfolio nowadays).
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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