search

openshiftio / openshift.io

Red Hat OpenShift.io is an end-to-end development environment for planning, building and deploying modern applications.
https://openshift.io
97 stars 66 forks source link

When creating a child work item of an epic that is already assigned an iteration, the iteration should be inherited #3966

Open rootAvish opened 6 years ago

rootAvish commented 6 years ago

If the parent item itself is a part of an iteration, we should automatically add it's child to the same iteration as well. If user has to change it, from say train/J to train/J/sprint#, they can always still do that but in most cases I'm assuming the iterations will be defined structured enough by the team where the iteration of the parent will be the iteration for the child (If I have to complete task x in 2 months, I cannot be completing one of its constituent tasks in the following 2 months).

GeorgeActon commented 6 years ago

@rootAvish this asking for a change in feature functionality. Good idea but not a bug.

rootAvish commented 6 years ago

@GeorgeActon This used to be default behavior in Jira and Trello, I assumed this was an overlook and so filed it as a bug, but if not then yes this is better marked as a feature request.

Veethika commented 6 years ago

@michaelkleinhenz @nimishamukherjee Has there been a previous discussion around this?

joshuawilson commented 6 years ago

This was either missed in design or dev. I can't see how this would be intentional. To me it is a bug. I have to set the iteration each time. Or sometime I forget and have to go back and do it. But I never want it left at the default top level.

@openshiftio/uxd-team please advise.