The challenge I am having is choosing a hierarchy of objects that keeps things simple, but at the same time provides enough detail to be useful. It's early days for us - we haven't adopted Agile practices yet at our company, but have been advised that Kanban is a good way of visualising bottlenecks and helping to improve our processes.
We have one main software product (so I set this up as the only project container in Jira) and several projects going on concurrently building on this. The problem I find is that Jira only handles two levels of task (i.e. parent object and sub-task). If I use an object to track the status of a project on an overall high-level board one level is already 'wasted'.
The ideal would be to have a 'parent' object to track the overall status of a project, then be able to drill down into these and see sub-tasks and sub-sub tasks for the various departments. I'm currently fiddling about with the Structure plugin and custom fields, but it is getting pretty complicated.
It occured to me that actually a 'project' for us is really just a version number (or release) of the product that can consist of all or any of these: new feature, bug fixes, refactoring improvements, infrastructure changes. It is already possible to assign multiple objects to versions in Jira (they appear in the roadmap tab and the classic GH planning board) so it would be perfect to be able to visualise these versions on a Kanban board (i.e. be able to apply a status to a version).
While I am not sure whether I completly understood your question, it appears to be me that you are want to visualize the flow of items which are belonging to a version.
Isn't Swimlanes the best solution for this?
Hello, thank you for your response.
We have the view of granular tasks you are referring to on the related project board (we have a separate board for each project) but we are after a high-level view of all projects.
As described, what we have done so far is created a custom object type to track these, but it would be a nicer solution to be able to plot the release as an object in it's own right.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
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