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

[Deleted user]

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

[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

[Hugo Rocha]

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.

[Hugo Rocha]

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.

[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.

[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?

[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

[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 

[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.

[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.

[Ory Zaidenvorm]

Indefinitely? You're sure about that?

[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.

[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.

[Test Everhour]

Hello. Does it possible to handle auto-generated(and obfuscated) css classes which changed each time on new update goes to live? I need it for  my browser extension. I can't embed in JIRA pages because classes are not static

[Jason Wong]

Hi @Edgar Miranda,

Right now when you have sprints disabled (this happens typically when you start with the next-gen kanban template) issues will be automatically moved from your board after they have been in the done column for 14 days. 

This doesn't mean that the issues are deleted. They are just no longer visible via the board, but can be found via Issue Search. 

We have improvements to this capability on our near term roadmap, where we plan on providing you the control to decide when you'd like to move issues from the done column, or if you prefer to leave them in the column indefinitely. One implication of leaving issues on the board is that it may start making your board very heavy - it will take a longer time to scroll to the bottom and the data loaded onto the board will increase. Just something to think about with leaving issues on the board indefinitely.