nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

G'day 👋🏼 I'm Jason Wong, Lead Product Manager for Jira Software Cloud, AMA

Jason Wong

Last month we formally announced the new Jira experience, which is a culmination of over a year of daily releases aimed to improve features, functionality, and overall value to our customers. We built this new experience in direct response to customer feedback - we heard loud and clear that our users want a way to get their projects up and running quickly, focus on the work that matters most, and move seamlessly between projects - and be able to do so in an intuitive UI.

We're not done executing on this vision yet, and want to hear your questions about what you've seen so far. Ask me anything about the new Jira experience:

What is it, exactly? Why? Who is it for? Does it make sense for my team?
What are best practices?
What's next?

Start adding your questions to this discussion (you can add before and during our live AMA), upvote others' questions, and stay tuned as I'll be answering anything that's on your mind about the new Jira experience on Tuesday, November 13th at 2pm (Wednesday, November 14th at 9am in Sydney). Hope to see you back here then!

Accepted answers

Warren_mz9b4z

The idea behind the new issue view is great, but there is a major flaw in it at the moment, to the extent that I keep needing to use the "See the old view" link. The problem is the long list of fields down the right hand side, in no particular order. I've seen large numbers of people on the Community forum complaining that the order needs to be configurable and / or bring back the tabs.

My questions are :

What is being done to address this?
What timescale can we expect to resolve this?

Until this is resolved, the new issue view is useless for many people. As an example, there is a team in my company that has ~50 fields - these appear in a random order and move around for no particular reason, so it's a nightmare to try and find a specific field.

Thank you for your time

Jack Brickey

A number of people in the Community is asking about Next-gen and Roadmaps for Server. Any discussion about that possibility?

Jack Brickey

Is there a good definition of 'New Jira 2.0' and what is includes. Most questions here deal with Next-gen projects but some deal w/ the new look&feel UI that is presented currently if Jira-labs is enabled. I think there is a need for clear terminology and definitions to help control the confusion people are feeling.

Walter Buggenhout

I believe that the goal to 'get people started quickly and easily' with their project is certainly being met. But on the other hand, I have some serious doubt about the 'moving seamlessly between projects' ambition.

As each team is free to configure its own project to their liking:

how should we deal with cross-project searching and reporting?
how should we make sure that we collaborate and not end up in a bunch of isolated silos on a per project basis?
supposing that most teams manage more than 1 single project simultaneously, how do we easily give them access to all their work in a single view?

In close relation to that last point, how would you define a 'project'? I am aware that the same challenge applies to Jira Server and Cloud (as it was) and Data Center too, but if a fully project centered approach becomes the standard, separating the configuration makes this a potentially bigger risk in my opinion.

M M_kz5g2p

How i can create ticket and automate ticket creation for build issues in jenkins? thank you in advance.

All comments

Warren_mz9b4z

My questions are :

What is being done to address this?
What timescale can we expect to resolve this?

Thank you for your time

Justin W. Arndt

Hi Jason,

One of my team was asking if the linked issues could show up on the cards in the card view. I know you're trying to keep the cards small, otherwise the visualization gets lost a bit, but that might be nice. Thanks!

Edgar Miranda

Is there a way to disable task being automatically moved out of the "Done" column after two weeks? I would like for everything that is Done to remain in the column indefinitely.

Jason Kolpack_2x1fjt

Is there a convenient way to mark issues as ready for the next state for a traditional pull Kanban flow?

Andrew Cato

How can I migrate my existing "classic" projects to the new "next-gen" projects?

Would love to use the new features, but if we can't migrate existing projects I don't understand how this is ever going to be used in my organization.

Jayme Rabenberg

We like a lot of the features associated with next gen projects, but since we've been using JIRA for years, across many team, for development projects on multiple platforms we see migration to next gen projects a very difficult hurdle to overcome. Can you provide any guidance to a company that wants to move to next gen, wants to reduce some of the complexity and overhead of projects, and enable teams to independently build their workflows and have the agility they need to refine their process, and needs to find a path to migrate their current classic JIRA projects to next gen.

Werner Anders

There are a number of features that are missing from the new jira issue view.

1. No share button

2. No drag and drop of file attachments

3. Custom fields get lost on the right had side

I find myself switching over to the old view to address these missing features. Is there a plan to bring back some of these features to the new view?

Abel Lineberger

How will the Portfolio product integrate with the new experience projects?
How will new experience handle Initiatives?
How will the new experience handle issue relationships / dependencies?

Will McCall

A few questions and requests around epics. Reporting, visualizing and templates. The addition of the road map feature is amazing!

1. In the Roadmap view i'd like to see issues completed/total issues in epic.

2. I'd like to create a report to see all open epics, # of issues complete per epic, start/due date. This might be possible via the share Roadmap feature?

3. Any plans for epic templates? We have a set of repeatable tasks per epic. Currently using issue importer for classic and need a more efficient way to do this. I'd also like to pass the control to the users rather than admins which aligns with your Next Gen strategy.

https://jira.atlassian.com/browse/JSWSERVER-7721

Jack Brickey

A number of people in the Community is asking about Next-gen and Roadmaps for Server. Any discussion about that possibility?

Jack Brickey

Sarah Elkins

I am also interested in this question. We currently host a large Jira Software Server Datacenter inside our company firewalls and would like to know if and when these features will be coming to that offering.

Kelley Lawton_vpz66g

What are the plans to support the Issues and Filters features? It sounded in the webinar as if there is no plan to support Advanced JQL queries, nor necessarily the full Basic Search features. Also, what about plans to support Bulk Edit of issues and CSV Imports? Additionally, will there be Epic and Time-tracking reports? These are all limiting factors which are keeping us from moving to the Next-gen project approach. However, I seem to be able to access some of those features from the main Jira Issues and Filters link (outside of the individual project), but the results are inconsistent (for instance, it looked like I could bulk edit custom fields that are not even in the next-gen project even when I was only selecting tickets from a next-gen project.)

Jack Brickey

I really haven't spent much time w/ Roadmap TBH but wanted to provide this feedback.

When I first looked at Roadmap I thought "Gantt chart". As such, I expected to be able to show/hide the children under the epic. This obviously isn't the case so i'm unsure how to really leverage the roadmap as yet.

Another oddity is that I can drag the endpoints of the epic and it will change my start and end dates. However, if I have children (always i think) under the epic then the dates can suddenly 'violate' the bounding epic start/end dates.

Steve Larsen

We have a template project set up with workflows, screens, custom fields, etc. that is used as the basis for new projects. When creating a new NGen project I selected the option "Share settings with an existing project" and the project created successfully.

However there are no boards created initially (the template has 2 boards). When I go to create a board in the NGen project, I am presented with 2 new options: Project (select 1 or more projects to include) and Location (select a Software project or your own profile as the place where this board will live).

Can you explain these 2 options and the ramifications of choosing an existing or new project/location? If this is documented please provide a link and I'll go read up on it!

Barry Flower_gsjdow

Can a link be provided to the NextGen Webinar on the 8th Nov so that I can share it with my colleagues please?

Ory Zaidenvorm

Indefinitely? You're sure about that?

Walter Buggenhout

As each team is free to configure its own project to their liking:

how should we deal with cross-project searching and reporting?
how should we make sure that we collaborate and not end up in a bunch of isolated silos on a per project basis?
supposing that most teams manage more than 1 single project simultaneously, how do we easily give them access to all their work in a single view?

Ory Zaidenvorm

Totally agree!

JJ_v8tv9j

100% agree with this one. Because of these limitations of the new issue view, I cannot transition my teams to the new Jira isue view.

Clair Lawson

A few questions from the webinar please:

Can we migrate open issues to a new next gen project - is there a link to the instructions for this please?

How easy is it to create sub tasks?

Can tests be created in next gen, as tasks directly related to an issue?

Are version numbers able to be assigned to next gen, or is each project a version?

David Snoddy

Dave in sunny Ireland here, in the same thought as moving the Backlog out to another tab via 'Backlog Feature' (LOVE THIS FEATURE) can we have a 'Aged Done Feature' out to the right. AIM to keep a concise display of current cards thus allowing us to concentrate attention on current work. It could be that the 'Aged Done Feature' would allow us organize cards by person, date completed date, etc to allow teams to see who or when rollout to production was complete. But i stress the main aim is to move the older cards that are done to a separate screen to keep as simple concise view

Elke Heinrichs

I llove the Next-gen features and the Roadmaps. Due to the fact, that we run a large server instance too, i also want to know if and when this features make their way to the Server Version of Jira.

David Hudson

I agree as well. I have to revert to "See the old view" on every single task I try and manage.

Francis Kus

This is also my greatest concern with next-gen projects...

Koen Vermeulen_aqa60y

I'm curious too! If Next-Gen is available for Server, when will the update take place?

Alex Galvan

Hey Andrew,

It is my understanding that it won't be possible to migrate classic projects to the new ones

Nilesh Patel

@Edgar Miranda Not sure I understand what you mean. I am new to this and just created a new Jira Next-gen project and have yet to introduce the project to a development team. Are you saying that at the end of a sprint tickets are being moved from one Status "Done" to somewhere else? Where does the ticket go?
Perhaps adding a bit more detail might be helpful (at least to me, a newbie)
Thanks.

Mirek

we heard loud and clear that our users want a way to get their projects up and running quickly, focus on the work that matters most, and move seamlessly between projects - and be able to do so in an intuitive UI.

Hi @Jason Wong

There is a BIG difference between giving permission to everyone to create projects, fields, workflows, issue types .. etc. and making life easier. Looking only at "next-gen" project which I assume are a new vision of projects in Jira and allow that I am not convinced that this is a good approach..

Simple example.. Business need 20 projects that are similar for each team. There would need around 15 similar custom fields, workflow with 7 statuses.. same group of people would be admins.. etc. and this is would be a standard for every new project also.. Could you please tell me how I can quickly create 20 projects and more with the future with same issue types, fields, permissions when using the idea of "next-gen" projects?

Why overall there was an idea of something like "next-gen" project? Who actually requested that? Users? Users would like to see things implemented that are requested 15 years ago on JAC and have hundred/thousand of votes, not spend time on a complete new solution that do not even have ability to use sub-tasks that they need to request again. It is like going back 15 years and requesting things that were already developed and should be a standard when releasing a product. I know that we work now in Scrum now and it is better to deliver something that is working than something that is good, but minimum set of features should be there. IMHO you should improve classic way of creating projects instead of implementing a new vision.

People are learning Jira features and paying a lot of money to get certified in different applications areas (like Jira Project Administrator) and when using cloud they soon would not be able to use that knowledge because Cloud is now starting to go it own path.. with the UI, features and addons even that for cloud are completely different than on server.. not quite intuitive UI as you initially think. It is getting complicated even for experienced admins to understand the vision and get up to date with all changes.

People are starting to get confused when talking about "same product" that is called Jira. When "Cloud" idea started Server and Cloud versions was pretty similar. Most od the people though that it is just the latest version of Jira with some small administration limits hosted by Atlassian on cloud solution and that is the only difference. Now with new UI and all the changes that gap is starting to grow, people are getting more problems, need to sacrifice many things migrating, do more manually..

From the marketing and sales point of view Cloud is a great solution, but if you are are going deeper into the technical details what is possible and what are the limits adding to that addons features that are also different .. you can get really frustrated..

This is on Cloud, this is not.. this only on Server.. this on both.. madness!

And another new things called Roadmaps.. this feature could be already developed for normal type of projects.. Why it was only done for "next-gen"?

And overall I agree with many other people here that this name (next-gen) is very bad.. It looks like it is something new, great and shiny but overall it have a lot of limits like overall Cloud is still having comparing to Server solutions. You can see how many confusion is out there looking at number of questions on the Community for example.

Nilesh Patel

Andrew,
Think you can use the Bulk change feature to migrate tickets from one old project to a new Jira Next-gen project.

Nilesh Patel

I would be interested in the answer to these questions as well.

Clair, for subtasks I think this is an upcoming feature (top on the list) that we do not know when it will be released.

Clair Lawson

Hi - yes after more research, sub tasks are not available yet. I am trying to work out if this is a show stopper for me or not at the moment. I think I will use next-gen for a few smaller projects initially and see how it goes.

Rico Neitzel

I'd like to add: are there any plans an epic's status can be automatically switched if the underlying issues reach specific states?

Rico Neitzel

Can't you just use another status for that?

Rico Neitzel

I'm waiting for it for too long: Will there ever be custom "release notes" templates available in cloud as they are available in server?

Will McCall

I missed this one in my initial comment. My colleagues request this all the time.

Edgar Miranda

That's correct, though I don't enable sprints on my board. So it acts more like a Kanban board. In this case, when items move to the done column they will hang around there fora 2 weeks or so and then be "archived" in which they will be removed from Done but you can still search for them.

Yes, indefinitely. At the moment I want it to function in a similar manner to a Trello bardo.

Terri Bartos

Roadmaps vs Portfolio? Does Portfolio come across to, or link with, this new platform or is Roadmaps a replacement for Portfolio?

unknown

Why did you take away important and very convenient keyboard shortcuts like 'o' and 'e' for opening and editing issues? This has reduced the efficiency of viewing and editing issues. Instead, you should have encouraged users to use more shortcuts.

Takeshi Ohishi

The new next-gen project looks good and promising (especially, the built-in roadmap view is great.)

I'd like to assign an Epic to tickets more easily (e.g. with a quick action by ".")

M M_kz5g2p

How i can create ticket and automate ticket creation for build issues in jenkins? thank you in advance.

Malavos

Why is "Log work" button not showing up in our board, but it shows on the app, in mobile? In the web, everything is set up, the permission was made global so everyone can "Work on issues", yet it won't show up on jira cloud/web. What's with that? It seems such a simple feature, yet it won't work.

Malavos

Also, an additional feedback. You said, and I quote:

we heard loud and clear that our users want a way to get their projects up and running quickly, focus on the work that matters most, and move seamlessly between projects - and be able to do so in an intuitive UI.

Jira is now really intuitive for who needs to work, fast, and get their issues done quickly. But for us who are making the issues/managing everything? It is pretty slow. Hell, even Azure DevOps is faster to setup now. The configurations are a mess. The admin panel is confusing. Sometimes you click on something belong to a project settings and you are removed from the administration macro-view, going to the micro project settings. Who thought that was a good UX? I was really disappointed to see that how so much good work went into the dashboard and board, but everything more "Inside" is a hot mess.

unknown

Hi Jason

In my 'Big Picture' Gantt Module (Plugin link)
I have some of my tickets expanding down into it's workflow status breakdown
And others are not expanding down - How do 'turn on' all tickets to expand?

Kind regards,

Jira Admin Customer

Rico Neitzel

I can absolutely second this! It‘s slower due to heavy ajax calls now which was faster before. Yes - the skeleton is loaded faster, but then it takes. Especially module rich pages take a fair amount of time.

I can also confirm that settings and where they’re placed is very confusing and I always have to look a while to find them.

zhangwei

I want to know Jira's future plans, new features, new versions, where can I find them?

Oskar Collin

I like to use some kind of "Ready for development" column as the first column in our kanban boards. But if I turn on the backlog feature and add something to the backlog in a next-gen project, everything that is in the backlog "board" has the status ready for development (which is the first column in the board but separated from the backlog feature).

If you have the backlog feature on, shouldn't the status for the stories in the backlog have the status "Backlog" and not the status of the first column in the board?

G V Shabareesh

How to Create Scrum Project using rest api from python.

def creating_project(self):
pro = self.jira.create_project(name='BiggBos',key='DB',template_name='Bug tracking')
print pro

it is creating a bug tracking project.

where as i have to create a scrum project like this. but i am getting an error.

please resolve my issue..

Thank U...

G V Shabareesh

How to Create Scrum Project using rest api from python.

def creating_project(self):
pro = self.jira.create_project(name='BiggBos',key='DB',template_name='Bug tracking')
print pro

it is creating a bug tracking project.

where as i have to create a scrum project like this. but i am getting an error.

please resolve my issue..

Thank U...

Alexis Jaillet

Hi @Jason Wong

Next-gen JIRA projects are looking good !

Two main questions from my side :

How to manage releases with next-gen projects ?
How to handle cross-projects releases with next-gen or current projects ? (without Portfolio)
- Cross-functional project A + B + C = 1 fix.version / client / release.

Thanks in advance !

rgsilva-aegro

I've mistakenly cleared the backlog filter and now it shows all the tasks, include done ones. How do I restore it to its original view? Pretty sure it was a default backlog view filtering, as I don't remember changing anything in the past.

Alvin Cruz_tqjk4p

Would love to be kept informed of this also. We have Zephyr in the classic version but cannot get it up and running on Next-Gen projects.

Nilesh Patel

@zhangwei this is the information that we all have.

https://www.atlassian.com/roadmap/jira-software

Jason Wong

Hi @Justin W. Arndt,

Having rich information available at a glance is definitely something we want to provide on the cards, and ideally we would like to go one further by making it specific to your team.

Like with the issue view, the card view has its own system that determines where specific content can be displayed and what type of content can be displayed.

As we build out the card system, it should allow us to provide you with more control on what information you have on your cards.

Here's an example of the kind of plans we have to expose more information on the cards.

Jason Wong

Hi @Jayme Rabenberg,

Firstly thanks for the huge interest in moving to Next-gen. We have a lot of requests for more help moving from classic to next-gen. We are adding some highly requested features, such as sub-tasks, more field configuration, and refinements to epics (which you can track on our public roadmap) and in the future we will be doing something to make the move easier.

You might also want to consider the timing of the move to next-gen. Many teams are always very busy, with little time to focus on tooling but there comes a time when it's good to do a clean up and reorganize. Perhaps a good time is at the end of a project, or on completion of a retro where teams want to change the way they work. I'd then encourage them to try a next-gen project, independently configure it to what works best for them and only once they get buy-in to the new improved way of working they might then do a bulk move of issues and cutting over to next-gen (here's the bulk change documentation to move issues over from classic to next-gen).

If there are things they need that they can't find, please come back to us and let us know what those are.

Jason Wong

Hi @Werner Anders,

The new Jira issue view is still being built to handle more and more complex functionality.

The share button is on our roadmap and will come back sometime in Q3 FY19.
Drag and drop file attachments should be working - you should be able to do this by dropping it anywhere on the issue (which would attach it on the attachment panel). You can also open the editor on the description / comments (which would attach it within that content area), or when you have the option to select media (there is a little drag and drop window).
Which custom fields get lost on the right hand side? All custom fields should be visible or, depending on your config settings from the project settings → issue type, would be under the 'show more' option. If you can provide a bit more info, we should be able to address this.

Jason Wong

Hi @Abel Lineberger,

Right now, Portfolio isn't fully compatible with the new project experience, primarily because we have re-imagined issue hierarchy in next-gen and are working with a new data model.

The new experience will continue to be built out from a hierarchy perspective, so that we can support levels like initiatives in the not so distant future!

Other issue relationships are still handled via issue links in the new experience.

Jason Wong

Hi @Will McCall,

Thanks for the feedback! We are so glad to hear you're enjoying using the roadmap. Reporting, and how we better surface the sort of information you've mentioned, is something we are exploring at the moment.
This kind of report is not available at the moment, but we can definitely take your suggestion on board.
The new way we have implemented hierarchy with Epics would allow for this. For example with the new epics you can easily rename them - something you couldn't do in classic. We'll take your suggestion on board for when we look into next-gen project templates.
@Rico Neitzel, I do think it would be likely that we'll help with completing epics when the underlying issues are complete, similiar to how we do that at the issue level when it's sub-tasks are complete.

Jason Wong

Hi @Kelley Lawton,

For next-gen projects, we will be introducing ways to get to customized views.

We will start with a more user friendly interface - similar to say basic mode in issues search (which builds the JQL for you in the background).

Raw JQL (direct text input) is very powerful, but not everyone knows how to write an expression and limits the ways we can simplify things.

For instance, you'll notice that in classic projects, you cannot drag and drop cards between the (swimlane) groups. This is due to having JQL defined swimlanes. JQL can be written in so many ways that it makes it hard to understand how to move a card between a swimlane. In next-gen you can drag and drop between your swimlane groups. We're aiming to retain this even when we introduce the ability to make customizations to your swimlanes.

Another example is, if you have a JQL defined classic board, it can also be hard to understand how to create a card that matches complex filters. When there are complex filters, often newly created issue sometimes will not be visible on the board, until you go and edit the issue's data to get it to match the board's filter. You'll notice that this no-longer happens with next-gen projects. Try selecting a few filters,

These are just some examples of why we're not diving straight into JQL just yet with next-gen configuration. It is likely that over time we will allow a JQL override for even more advanced filtering that cannot be achieved with a simple but more powerful filter builder.

Jason Wong

Hi @Jason Kolpack,

Here are a few ideas on how you could mark issues as ready for the next state:

Move the issue to the next state, but leave it unassigned (so it is ready for someone to pick up);
- If you view your board by assignee, this would clearly distinguish between assigned and unassigned issues
Assign the issue to your next teammate but leave in the current state, so they know to drag it over when they are ready;
Use labels to make visible on the issue when work is 'ready for next' or such.
@Rico Neitzel's suggestion might also do the trick.

I hope this helps!

Jason Wong

Hi @Jack Brickey,

New Jira has a lot of updates and so I can understand your confusion around the various Jira brands and differentiating what is what.

The "New Jira 2.0" encompasses the new next-gen project experience and the refreshed look and feel. We have been releasing the new features and UI over the past several months and will continue to do so as quickly as we can.

When we think about the Next-Gen project experience, these are the key new features:

Roadmaps
Customizable, drag-and-drop boards
Project-level configuration
Redesigned issue view
Improved mobile app

Check out this page for more details about each feature: https://www.atlassian.com/software/jira/whats-new

Jason Wong

Hi @Steve Larsen,

Thanks for your feedback. When you select the option to create a project using the "share settings with existing projects" it creates a classic project. Currently we don't have a way to create a new next-gen project based off an existing project. However we plan to introduce templates which will allow you to share project configuration between projects.

Jason Wong

Hi @Barry Flower,

Absolutely! You and your teammates can access the webinar on-demand here: https://www.atlassian.com/webinars/software/the-new-jira-begins-now

Jason Wong

Hi @Walter Buggenhout,

Thanks for your feedback. We plan to introduce the notion of templates that will allow multiple projects to share configuration like IssueTypes, custom fields, notifications, workflows etc.

We also see a lot of teams who work across a number of other teams / projects and so we will also be providing cross-project views to those teams.

Next-gen projects have completely rebuilt configuration and so we've started simple by going project centric, before expanding into more advanced cross project use cases that introduced added complexity in implementation, say due to a board having cards that derive configuration from different projects. We'll get there though, so please watch this space!

Jason Wong

Hi @David Snoddy,

Great question! Glad you'd enjoying the new experience over in Ireland.

Having a place to see completed work is something we're looking to improve. Currently when you have sprints disabled (kanban style) the cards clear the board 14 days after they reach the last column. If you scroll to the bottom, you can then access Done issues using a list view. With scrum the issues are cleared after you complete the sprint. You then need to go and search for issues in the project that are done to find them.

We have a feature called "Releases" on classic projects. These are optimized for Versions, but we are looking to improve this in next-gen by modernising them with the integrations we're building with CI/CD and feature flagging tools so that you can get a great view of done issues with deployment information, so that it's a whole lot easier to see when things were rolled out to production. I'd imagine there are many other questions when looking at those done issues so we'll consider also the kind of views you suggested.

Jason Wong

Hi @Jack Brickey,

For our first version of the roadmaps feature, we wanted to start very simple. However adding the ability to view child issues is something we're currently exploring.

With regards to the dates set on child issues, do you currently set due dates on your stories/tasks?

Currently we treat the dates set on epics versus any story-level dates set implicit (eg., assigned to a sprint with a date range) or explicit (due date is set) entirely separately.

What would be your expectation on how this would work for your use case?

Jason Wong

Hi @Mirek,

There's indeed a lot of change here and we'll work to make the changes a lot smoother and more clearly communicated.

The first thing I'd like to address is that the new features we've built into next-gen go a lot deeper than UI change. There are data model changes that means features like Roadmaps do not work on classic projects. We took the opportunity to build on a new platform design using what we've learnt from customers and optimized for Cloud, for instance reliability and performance improvements have been a big benefit.

Next-gen has what we call project independent configuration. A lot of admins had asked for the ability to delegate project configuration to those in the team to let them self serve and make changes faster.

We're anticipating that you'll need a way to scale and also control implementation just like with classic project schemes but in a way that is a lot easier to administrate and so we'll help you create projects that operate with the same issue types, fields, permissions - more centrally administrated - when we build templates for next-gen projects.

Most discussions I’ve had with experienced administrators have ended with a view that it is far better to get the data into Jira, and that allowing anyone to create a project and administrate it encourages the data to be put in the one place inJira, rather than have it remain scattered or hidden in various tools, documents or spreadsheets where the knowledge or data is dark and disconnected. We believe that this open approach give organizations better visibility, promoting efficiency and innovation.

Admins have then seen how this gives them the opportunity to sort out knowledge and data management in more strategic ways through developing practises and education that drives overall organisational effectiveness to the next level.

Jason Wong

Hi @Terri Bartos,

Roadmaps provides a very different sort of solution for teams - it has much less depth in terms of functionality than Portfolio. If you have very simple roadmapping needs, then perhaps it could be a replacement for you. However if you still need something that is more in-depth, then we recommend Portfolio.

Jason Wong

Thanks for the feedback @[deleted],

Keyboard shortcuts are on our list and we will be putting them into next-gen projects to help you power through your work.

Jason Wong

Hi @M M,

You can use our Jira APIs to automatically create issues and use that with other applications.

However, if you are looking for something easier for Jira to provide, such as automations that would have a different answer.

Would you like to have a chat directly with our team?

We would love to know more about what you are trying to do and how we can help make that possible

Jason Wong

Hi @zhangwei,

Yep - the link provided by @Nilesh Patel is the right one. Thank you!

Jason Wong

Hi @Alexis Jaillet,

We will be adding in a way for you to get to completed work and manage that by introducing something like Releases in classic projects. You'll find that when we do that, it will not only have a way for you to look at Releases by versions, but by using integrations with CI/CD and feature flagging tools. you'll be also able to get a view of what you've released to customers when you are continuously deploying code to production or managing feature availability with flags.

Cross project will come to next-gen later on once we've built more features to cater for single project use cases.

Oran_Dennison

I love the vision of releases + deployments + feature flagging in a single unified experience. This is what I get most excited about seeing in next-gen projects.

Hopefully you include support for Bamboo builds and deployments since Bitbucket Pipelines aren't available for Windows-based projects.

Jack Brickey

thanks for the response @Jason Wong. For dates on roadmap given this is an entirely new concept in Jira I don't have any historical data. That is, in the classic projects I only use dates on stories/tasks/sub-tasks. Epics are simply containers for my work. An epic certainly spans multiple sprints and also releases. I don't worry w/ the end-date of an epic as it isn't really important.

However, in the new Roadmap epics take on a slightly more important role where dates become important. That is, for me, dates in traditional roadmaps are important. So, when you display an Epic in gantt fashion, my assumption is that the tasks contained w/in the epic must remain in the boundaries of the epic or more accurately the Epic timeline needs derived from the children, i.e. the earliest start and latest end date.

I hope this makes sense, if not feel free to reach out to me (you have my email) and we can discuss further.

Jason Wong

Thanks for the feedback @Takeshi Ohishi, we're really glad to hear it.

We're working on how we can make it easier to assign epics to issues, similar to what you mentioned - stay tuned.

Add to epic.png

Jason Wong

Hi @Rico Neitzel,

Regarding the "release notes" templates in Server that you're referring to - we still have the same release notes feature in Cloud for Classic projects https://community.atlassian.com/t5/Jira-Software-questions/Release-notes-in-Jira-Cloud/qaq-p/653264

Is that the feature you were looking for?

With next-gen we have yet to build our the new releases section. The idea would be to improve it from giving you a Versions based view of releases, to ones that can track continuous deployment and feature flagged releases. It's a very common use case to then take that to communicate the changes internally and externally so we'll keep in mind some sort of way to do this.

Rico Neitzel

Hi @Jason Wong

the question is about custom templates for release notes. Currently you can take it only as it is. You can’t add custom fields‘ output nor change the way, html is generated.

that is possible with jira server but it is not with cloud.

rico

Nilesh Patel

@Jason Wong
I would be interested as well in knowing how to call the Jira API?
Where can we find documentation on the Jira API?
Also does this Jira API work with Next-gen Jira projects?

Warren_mz9b4z

Hi @Nilesh Patel

The documentation for the API is here.

I haven't used the Next-Gen projects, so can't say yet whether you can use it for them, but it works really well for classic projects. I've just tried an API call on a Next-Gen project and it does return data, but that's not to say that every API call will work

Justin W. Arndt

Thanks @Jason Wong! Great to hear. (The image didn't seem to come through on the website...)

Mirek

Hi @Jason Wong

Thank you for replying.. Let me continue the conversation (if I can of course )

The first thing I'd like to address is that the new features we've built into next-gen go a lot deeper than UI change. There are data model changes that means features like Roadmaps do not work on classic projects. We took the opportunity to build on a new platform design using what we've learnt from customers and optimized for Cloud, for instance reliability and performance improvements have been a big benefit.

I understand that if you want to promote Cloud to have more users, usage and sales it means that you need to create a "light" version of JIRA. That is obvious. Standard JIRA Server added to AWS/Azure is not optimized well and you need to do a lot of request to do things that should be simple... And on cloud infrastructure of course you pay for everything (data, storage, transfer, ... ). What I do not like is that instead of building something more generic is only done for one platform (Cloud, Server or Data Center) and you still say that this is the same product.. It is starting to not be be same product. The idea is, but not the product.

Next-Gen project idea for me is Jira 2.x or even earlier when not much was possible but at that time Jira was a lot cheaper solution than now. Of course you have many things right now on your roadmap that would make soon this idea great (like templates, adding sub-tasks, import/export, sharing, workflows enhancements .. etc) .. but when? 2020? 2025? .. People need to wait again for many basic features and figure out workarounds to handle their work. They pay money every month for every user and expect to have a complete product. In addition they are starting to get lost what solution is the best for their business.

In JAC you have duplicate requests for Cloud and Server so that people could vote on.. That is a little bit affecting visibility what is important for people overall. From Jira they expect this and that .. why they need to divide between Cloud and Server all the time and see that something is implemented for Server, but not Cloud and vice versa and wait another few years to see this in a different platform. Some basic features should be the standard when releasing even if implementation time is different for every platform. It is like serving food for everyone in a good restaurant that are sitting at the same table.. not dish by dish so that everyone is eating at different time and other hungry are just looking. It is a matter of professional approach to the customer and serving at once!

Please remember that when designing all new feature to be flexible and delivered on all platforms. The implementation on Cloud could be the light version but the experience (features available) should be the same on all platforms. So no matter which version and platform of Jira you use you get the same features and ideas. That is starting to get lost somewhere..

A lot of admins had asked for the ability to delegate project configuration to those in the team to let them self serve and make changes faster.

By saying a lot of "admins had asked" it does not quite follow my feeling. I am a experienced admin and I do not feel that many people asked for that kind of "new features". I am working for almost 10 years on Atlassian products support and here on community I know what is the level of people knowledge, what they want to get from a project and what I personally want as a admin that would speed up my work to give them a good working project without asking ton of basic questions on community that they should find easily in documentation. That is all about self serving. It just does not work and would not work until product itself would be really intuitive. And just a proof of that I see a big increase of questions asked about next-get project. There are many limitations, documentation is poor and instead of improving experience it is on the same or even worse level. If people are asking many questions about a feature that is really simple this mean that there is a big need for something better or they still cannot easily (or fully) use the product or product have many limitations and bugs that are nor fixed in a expected time. For example they cannot even do a basic thing like migrating easily from classic to next-gen and back if they do not like them ..

Most discussions I’ve had with experienced administrators (...) We believe that this open approach give organizations better visibility, promoting efficiency and innovation.

Open approach is good but where is the "stop" sign? What would be the next level that is promoting efficiency and innovation. Giving to normal users ability to install marketplace addons so that they can extend their products easier and faster?

Admins have then seen how this gives them the opportunity to sort out knowledge and data management in more strategic ways through developing practises and education that drives overall organisational effectiveness to the next level.

I would like to underline here that we have System, Application, Project and even Board admins in Jira.. We should know about which "admins" we are talking about since every group have different needs, visions and knowledge.

For experienced project admins it is mostly true that are asking for more permission than only viewing the schemes in Jira. But on the other hand they do not care that for example number of custom fields are the most affecting performance in Jira. So if we could now give permission to create custom fields by project admins it might end up with thousand of fields, lot of duplicates, lower performance and overall a big mess in Jira instance that was until now properly managed and optimized by small group of certified admins that create projects in minutes.

If you have a big organization with thousand of users (that mostly have some standards of creating a projects and managing them) and want to still be open you might end up as admin with ongoing cleanup of unwanted projects, custom fields and other objects.. The additional problem is that in Jira there are no existing or new tools (except the new Custom Field Optimizer -> for DataCenter platform only again!) that can help admins administer Jira in easy and quick way. Instead helping admins in that way I feel that they would get more "non admin" work and spend much more time explaining to users what they can instead of doing that for them based on requirements. This is not quite the "next level".

Nilesh Patel

@Jason Wong There are a lot of good points that @Mirek is making.
There does seem to be a lack of consistency.
It would nice to be able to have a away to transition easily from Classic Jira Cloud to Next-Gen Jira Cloud, a simple example is that we cannot link issues between Classic and Next Gen Epics (with Stories and Bugs) having this allows us slowly move from Classic to Next-gen. Otherwise it is an all nothing choice that we are left with.
Currently there appear to be many key features missing a regressions of features already deployed such as custom field not even being visible.

So providing a detailed roadmap will allow your customers to help determine when to make the transistion from Classic to Next-gen.

Thank you.

Jason Kolpack_2x1fjt

Another status is what we are currently doing, but in order to keep the work in progress limits accurate we have to combine statuses in one column. You then lose the ability to drag issues between states which is a nuisance.

I can think of a number of problems with trying to manage it by using the assignee. We've found workarounds that mostly work, but in a prior role we used Agile Central which made the process much more natural.

I would think doing something like adding a ready flag to the issues would be the best option. I tried doing this with a custom field but again, was not optimal as there didn't seems to be a great way to add a boolean field. We ended up having to add a Yes/No dropdown which ended up being a little confusing.

Kelley Lawton_vpz66g

@Jason Wong Thanks for the reply! What about Bulk Edit of issues and CSV Imports? Saving filters? (even just Basic filters)? Will those be supported in Next-Gen?

Jason Wong

Hey @[deleted],

I'm afraid I'm not an expert on all the apps in our Marketplace and it sounds your question would need Big Picture involvement.

Marketplace vendors provide support and community links in their profiles so I would recommend you reach out to Big Picture directly

https://marketplace.atlassian.com/apps/1212259/bigpicture-project-management-ppm?hosting=cloud&tab=support

Jason Wong

Hi @Oskar Collin,

In next-gen projects, all the statuses that are available are represented on the board. For example, the way to create a new status is to add a new column to the board. Since there are no statuses that are not present on the board, there is no way to have an additional status right now that is only visible on the backlog.

The other thing that has changed is that we have aligned the way the backlog works so that it’s consistent, whether you are not using a backlog at all, use only a backlog, or use a backlog with sprints.

In classic projects these all worked in slightly different ways, but in next-gen projects sprints and backlog can be added to (or removed from) the project as independent features. To make this a seamless experience, the backlog now behaves a bit more like the old scrum backlog used to work, where issues could be on the backlog in any workflow status.

For your use case, I would recommend that you create a column called something to describe the status you define that comes before something is "Ready for development" eg. Triage and make "Ready for development" your second column on the board.

Jason Wong

Hi @Kelley Lawton,

Yes we'll need to make sure those work and yes there will be a way to save filters - that's what I was mentioning above how we'll make that more user friendly through a basic filter kind of interface

We will start with a more user friendly interface - similar to say basic mode in issues search (which builds the JQL for you in the background).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

ask-me-anything