JazzHub beta 3 - Create multiple release
Accepted answer
We simplified the user experience to only allow one release per project at this point. We do have plans to revisit this and see if we can allow users to easily create more than one release.
Comments
Lauren,
I understand that we want to simplify the UX, but if only one release is allowed, then why having a release at all?
Releases makes sense when you have multiple ones. If you don't then you should only have a backlog and a set of Sprints
I believe we chose to to contain the sprints inside of a release to allow for the possibility of multiple releases in the future. On your project's main page, the timeline displays the sprints as though they are the only release. Are there specific places in the UI where you find it inconvenient to have the sprints listed under the release?
Sorry Lauren, I missed this answer. Probably too tired after Innovate.
Ok, I understand your point: Releases may be supported in the future, and then, having multiple Sprints within a release makes a lot of sense.
All I am saying is that for a user, it is weird to see a "release level" if you can not create two or more releases. A Scrum team will probably never use 1 and only 1 release. The team will use no release at all (only Sprints and backlog), or 2+ releases.
Makes sense. I've added your comment to our work item tracking this.
@Lauren, are you still working on adding releases to JazzHub?
I'm no longer on the JazzHub development team, and I'm not in the loop with their plans. @agarcher - can you provide any details?
showing 5 of 7
show 2 more comments