I will however add that Classic and next-gen project differences run much deeper than just UI changes - as you mentioned, there's organizational timing (in that I mean, your organization) that we need to consider and a lot more complex data migration that would need to take place and so in the future if we do have to make changes, I can assure you that it can't and won't be done quickly.
Thanks. The UI changes probably wouldn't block upgrading or impact our current process. A number of the other changes might prevent us from upgrading (based on what I've been reading). My level of stress dropped off considerably when I was informed there will be no forced upgrade. 8-)
Guys! Seriously? No logging time? I literally just migrated a project to the new look to give it a go and there is no time log feature? How am I supposed to bill clients when staff cannot log work?
Now I will have to migrate everything back. Really helpful when already extremely time poor. Thought this new version was supposed to help us be more agile, not less.
Yes, I am tired and grumpy but it is late on a Sunday night and this is the last thing I needed.
Maybe don't release half written features in future as a "New" version? Maybe - call them "Beta" until all appropriate functionality is available.
I believe you can add time logging by going to Project Settings - Issue Types - and then drag a "Time" field to the issue, call it "Time Logged" or "Logged", before you migrate back.
Where is releases in all of this? Currently i get the sense that one project is one version for next-gen, which does not make much sense if you have few smaller releases in between you will end up with hundreds of releases.
Atlassian Team members are employees working across the company in a wide variety of roles.
November 6, 2018 edited
@Vanessa Barrett apologies we didn't set the right expectations for you moving your work into a next-gen project. We are building out the power of next-gen over time and time logging will be something we look to do in the future. You can see what we're working on right now and what's coming next on the public roadmap https://www.atlassian.com/roadmap/jira-software
We'll continue to improve on how we make this information available up front when people create next-gen projects, to ensure they have the right information as to whether next-gen is the right choice for them at that point in time.
Is there a way to have more than one assignee at a time? More specifically, I'm looking to set up document training where I need multiple people to denote that they have read it and are trained on the subject.
as said before, really love how simple everything is now... one of our main pain points are the absence of releases//versions and sub-tasks (already on roadmap) ...
Is there any eta when we can expect the versions//releases feature?
Hi, couple of questions hopefully someone can answer!
1. Is there a way to group tickets on the board according to priority?
Currently only able to group by "None" "Epic" and "Assignee"
2. When I switch on the backlog and sprint features, it resets the current board, moving all issues in progress/to do/done to the backlog regardless of their status.
I had thought perhaps activating the backlog feature might open up the possibility of grouping the board by priority, but this seems to replace the board entirely.
We love the simplicity of the new next gen project and we use it effectively, but it seems odd that we are unable to organise the tickets on the board by priority.
can I please draw your attention to actual integration of next-gen projects with "abacus"?
It does not work.
I already raised the issue with Mumo Systems and had a good discussion with their support anyways it seems that due to the new architecture of next gen projects linkage between issues and epics is lost. This affects E.g. "Issue Rollup to Epic" functionality.
Keen to use, but migration is critical to me. Losing project information through transition is a show stopper. Things like application links and hooks into other tools especially with confluence will cause too much disruption. Is more full feature migration on the roadmap?
144 comments