Walter Buggenhout Community Champion

Hi @Subha M , Depending on how many assignees you have in you project, you could try the Recently Created Chart: The chart will show you issues relative to the moment they were created. Red is still open, while green is resolved. Each segment of the chart can be clicked to view the underlying issues. As input, you could…

No, not necessarily. By default, custom fields are hidden from the issue view screen as long as they don't have a value set.

Hi @Veronika Dvorska , 100 is 100%. In simple words: time spent is more than the original estimate on the issue. This is standard jira functionality. Although in JQL you query for it as 'workratio', you can add the field in the issue navigator as 'Work Ratio' (spelled with 2 words): On dashboards, you can simply display…

It's a service desk ticket for now with ref CA-871319. 

A ticket has been created for this issue.

Hi @Priya Gopinath , Depending on how many projects you are talking about, your second option would definitely be the most beneficial towards the result you are aiming for. When you connect the new schemes to your existing projects, Jira has a lot of built-in functionality to neatly migrate your existing issues to the new…

Hi @David Anthony , I think you are right that there is no good trigger available in JSD automation for the use case you describe in your scenario. Maybe you can raise a feature request for it. Solving your case through workflow is not an option either, because your automation should be triggered through a transition then.…

On top of your screen scheme, you also need an issue type screen scheme, which associates your screen scheme with the issue types in your project. From your project configuration, it is the list of issue type screen schemes that you can select, not the screen schemes.

Hi @John G, If you want the assignee to be unassigned by default, just remove the assignee field from the customer portal's request form. 

Hi @Mukesh_Nandan , The best place to start should be Atlassian documentation. In the top right corner of the page, select your Jira server version. Good luck! 

Hi @Mathijs Delva, Not by default. Tempo (Timesheets) is an app from the Atlassian Marketplace that you can add to your Jira Cloud instance.

Hi @Andreas Astrom, You cannot manipulate the SLA system, as it is based on a timer that gets started, paused and stopped by event triggers (issue creation, status transitions, resolution being set). How about setting a due date / time in a dedicated custom field for this specific use case and then using JSD queues based…

Indeed. I'm afraid next gen projects do not support updates to closed sprints yet. In classic projects, you can reopen a sprint from the Sprint report, but this is not fully featured yet for next-gen projects. See also this community post about the reporting 

Hi Bernadette, It seems you can. In the backlog view of your board, find the button with the 3 dots next to the sprint's name. There you can edit sprint details and even delete the sprint:

Does anyone know if/when recordings of Open sessions will become available?

Really the very best I ever had must have been in the Belgian restaurant Nuances of chef Thierry Theys. The guy has an amazing passion for food and spends like 2 hours (or more) to prepare a single piece of tuna. Which leads to something like this: The mix of textures, flavours and even temperatures in the man's dishes in…

@timothy odusami, Lead Time is different from Cycle Time as it starts when a request is created and ends at delivery. Cycle Time starts when the actual work starts. 

Hi @Shelly Weber, If I understand you well, there's 2 sides to your question: * process: you are doing modifications to stories that are already being developed; * technical: you cannot make changes to stories once they are in a certain status In terms of process, it seems weird that you are still making changes to stories…

Hi @Jason Huntowski, Sprints are a feature of a board. And although both status and resolution both have a clear relation to what people consider 'done', for a sprint board this is just everything that is in the rightmost column of your board. 

Hi @Frank J. Øynes, Your releases (or fix versions) are project specific in Jira. So no, it is not possible to associate issues from project B to a fix version of project A. 

Hi @dilipkumar23bytes, Make sure you get yourself familiar with what the tool is about, what you could use it for and what resources you have to help you out. A very good starting point could be this Jira Cloud Administration guide. It gives you a lot of context and many many links to resources that help.

Hi @Brian, Most likely through an asset management / CMDB app. Although not many, there's a few options available or coming to Jira Cloud. Have a look at the Atlassian Marketplace. 

Hi @Randy Pickus, Not by default, but you could build yourself a filter and have it send you notifications from a filter subscription. You can read more in this related community article. 

Hi @Scott Barone, Seems your question is a couple of weeks old already. I am quite sure there's no technical blockers for you to set up the hierarchy you describe. To be honest, I have not ran into a real life situation yet where this has been implemented as such. The most important risk I see, is that you can only…

Hi @Lydia Thompson, Have you checked what the data source of your initiatives is? In most cases, they are stored in a separate Jira project. It could be that the users you are referring to don't have access to them in Jira. Make sure your new users have browse project permission in the Jira project that holds your…

Hi @Anney, If your subscription is cancelled already, it will no longer be billed. The site will be deactivated and removed automatically in a couple of weeks. For more information about the process, see this support article. Sorry to see you go!

Hi @Dillon MIller, If those approval steps need to happen in stages, why not provide 2 statuses in your workflow: * Awaiting Management Approval * Awaiting Director's Approval This would lead to 2 consecutive approvals in the process. 

Hi @Miguel Belen, You should make sure the due date field is available for your Service Desk project, as described in the documentation: For this SLA to trigger, configure the Due field to display on the Issue type screen, and set the Due field when the issue gets created. Check out this page to learn how to set this up.

Hi @Pall, Seems you are after Cycle time metrics. With Jira out of the box, you could do this with the Control Chart. All you need is a kanban board that holds your data and an optional quick filter to select the certain issue type you are after. The control chart is not available in next gen projects. So if you need…

Great news! Well done, @[deleted]!