@eoinh to your earlier request around how people are using components, we need them for time tracking across projects similarly to the way you’d use a custom tag or label, because it’s one of the few objects we can structure tempo timesheet reports on, essentially we use it to categorize an issue in Jira and then run tempo timesheet reports by those groupings. We could use labels similarly if tempo would offer them as a grouping notion for time reporting.
Man, it'd be really cool if your Server customers could get this same functionality. As it stands now, we're locked into purchasing expensive add-ons to get basic roadmap functionality. Are there any plans to bring next-gen projects to Server (please say yes)?
@Rayen Magpantay Our team have been adding a large number of items into a roadmap, some of which are ideas, some of which are in progress, some are scheduled to do. Am finding the filtering to be very limiting since it only uses the three default issue statuses (TODO, In Progress, Done), instead of the ones you define for your board (for us this is 10 statuses). It would also be greatly useful to us to be able to use the full set of statuses alongside labels to filter items on the roadmap.
This would allow us to:
- dice the data anyway you want to filter the epic roadmap view so you can have conversations about it (works fine as is for small roadmaps, not so much for large ones)
- replicate release / fixVersion from classic by using a label so you can see which roadmap items fall into which release
- actually use it as a planning tool so if your epic / feature is "in design", the design teams knows which ones they are planning to accomplish in a time period, etc...
It just makes that roadmap view that much more powerful.
We should definitely have VERSIONING and RELEASING features !!!
That would bring the whole chain for a product management because the Roadmap feature is good but having the opportunity to manage and control the versions of your products/projects, having them linked to your epics and the roadmap is better !
We often have ad-hoc/emergency changes as we are both development and operations. A parallel sprint would allow for us to accommodate this, but not if we can't run them in parallel.
Any other suggestions for operational tasks, until this functionality is there?
Really important for my agency to have Time Tracking functionality! Mapping time spent on each issue and having report to view it all is critical to managing projects.
Create a branch in git -> Moving the card to 'in progress'
Opening a PR in github -> Moving the card to 'code review'
PR merged -> Move the card to `product owner review`
Moving the card back to 'in progress' -> Reassign card back to original developer (not the reporter or the current assignee..!)
Is that part of the roadmap? I read the roadmap but I couldnt find anything that sounded like it. (Theres stuff about jenkins build status integration but that sounds different)
Configured notifications will be key - I can't ask my business users to log requests only to inundate them with every ticket update. I don't see any notification configuration currently available. I may have to move off the next gen board in order to roll out use of the board to my user base. thx.
We need the ability to have more then one board per project, as there are teams within one project that don't want to interfere with workflow of other teams board.
Hi! I am really into the next-gen project, but i was wondering if it is possible to change the colorcoding of statuses (grey, blue, green)? And the little circles (grey, blue, green) shown on the backlog-screen don't seem to work right now, am I right? Thank you!
It doesn't look like there is a way to update the workflow or workflow scheme for a next-gen-project. When is this being resolved? Or am I missing something... I have looked at your roadmap. And I don't see it on there.
I would also like to see a way to change the color of workflow items other than grey, blue, green. I'd like to add to the workflow BLOCKED. And have that show up in RED. So that it's easy to find and you know you need to prioritize whatever is blocking an issue.
We recently migrated from Trello to the Jira next-gen project board - the migration was fairly painless (though we did had to rerun it as it failed a few times). The Jira next-gen board is a good fit for us, but it would be really useful to have the following changes / issues tackled:
the issue resolution field is always listed as unresolved but there doesn't appear to be a way to change the resolution status or define it
there's no component field, so no way to group in requirements management add-ons (e.g. integration with rmCloud)
ad-hoc checklists - even Trello had this by default, yet missing in next-gen (a must-have feature!)
when exporting issues, custom fields are not included
ideally a way to baseline/version the board
project lead can't be changed
It would also be great to see a rough timeline on new roadmap feature to give us an idea how soon or far out they may be....
This is going to end up being the same as normal Jira 😂
If I could use Trello I would. Trello is so flexible. It probably would have been easier to add reporting to Trello and charge for that, than to try to make Trello inside of Jira, which is what seems to be happening here.
I think the point of next gen projects was probably to try seeing how simple a kanban board could be. For me Trello is way more usable, but others in my organisation are very used to Jira. We just use the Kanban board with swimlanes, components and labels in normal Jira and it does the job.
can you create a next-gen board from a filter. We have epics across different projects and it would be epic ;) to create a next-gen board displaying all these epics.
118 comments