Fernando Bordallo Atlassian Team

I love this post! Truly actionable and example-driven. Kudos! ❤️

This is great! Thanks for sharing @Kjell Tore Guttormsen 

Hello @Merve Tuncer There is no one single way of running this play. Every iteration will change how the team plays out its role and follows the guidelines. I would recommend you don't overthink the order or try to enforce 'forgetting' cards. Try it, make sure you have a 5-minute conversation at the end of your session to…

Good catch @Josh Allen 👁‍🗨

Hello @Veronica da Cunha Diniz I believe your question has been incorrectly placed as this section of the community is focused on the Atlassian playbook. You might want to repost your question into the Jira Software channel

Hello @Natalia Fernandez Cortes In my experience, when running this meeting, the process does not include specific scales given the nature of the conversation you are usually trying to spark. It becomes a matter of having an open conversation about scenarios you can envision where two or more areas of impact or values come…

Very good answers here @Arkadiusz Głowacki thanks. Can you share the top issues or change aversion situations you have dealt with when introducing or setting OKRs?

Great info for the coming year! 🙇‍♂️

+1000 to both comments. Failing fast is hard to ask but not doing so knocks on the door of bigger failures. 👍

Is there an ETA for the content? 😬

Interesting. I'll surely take a peek into how my team can make use of the Release train

Hello @Dev As you mentioned, you can control higher-level access to projects with user groups, limiting the visibility this user has into classic projects. In next-gen, user permissions are controlled with the project's access level configuration. You can change the access level by going to the next-gen project 'Settings >…

Hello @Tom_Schwarz this is a feature that has been requested in the past and is in the backlog for future development. You can follow this ticket to track advance: https://jira.atlassian.com/browse/JRACLOUD-71937

Hello @Marcelo Cajueiro There might be two ways to go about your wanting to test next-gen: * use the data generator plugin * create a classic project with sample data and migrate it to next-gen. See this thread for…

Hello @Tom_Schwarz This is a feature that is currently being implemented and will roll out to production in the near future :) I can't give you an exact delivery date but it will definitely be within the close next month/s

Hello @Robert Masur Sprints are an interesting part of issue history. An issue can be in several sprints at the same time from the JQL point of view given they maintain history from previous sprints. This is to say, if an issue was part of an old sprint and then was take to the next one and so on, when searched through JQL…

Hello @Farbod Jahan Unfortunately currently changing the order of the quick action buttons on the issue page is not a configurable option. You can create a new feature request/proposal here: https://jira.atlassian.com/secure/Dashboard.jspa See the steps in the section 'Suggest a feature'.

Hello @korovin.ds According to the first image you have attached (Jira), your user is not logged in and you are attempting to view the projects list page, which will most likely be restricted. Once you fully log into Jira, you should be able to navigate the app as usual.

Please check this thread - https://community.atlassian.com/t5/Answers-Developer-Questions/Cross-Origin-Resource-Sharing-with-JIRA-REST-API-and-Javascript/qaq-p/484801

Hello @Dionei Piazza I'd sit more on the side of 'multiple projects', one per squad. It has great benefits and aligns with the needs you present: * easier to configure and for each squad/team to evolve their process independently * workflows, labels, field management, ... stays in the team * backlogs don't mix, which can…

uHuhh nice! I'm going to say #2 is the lie

💥spot on ;)

Hello again @[deleted] I see. That being the case I would recommend that you do the "heavy lifting" outside Jira. Two ways I can imagine I'd deal with this scenario: * create a script to send JQL queries to the REST API, requesting the issue information based on date ranges. Then export to CSV and manage in google sheets *…

Hello @Rudrama Devi Thank you for posting your question in the community. In order to generate REST request against the Jira API you will need your application to be authenticated. You can find details on how to do this in the official documentation…

Hello @Andrew Duplyakin As Scott well mentioned, the navigation pane is static. Also, there will be a release (very soon to come) of an improvement to the Jira navigation system as a whole, which will include the topBar navigation system. Here is the link to the extension you can install to try this out in the…

Hell @Will Bebee Given you are working with a next-gen project I'd recommend you add new statuses through the board itself as new columns. You can then add transition logic by adding 'Rules' to the board. This you can access by click on the meatballs button at the top right of the board view and then clicking on 'Manage…

Hello @[deleted] Indeed this sounds very much like the velocity chart report. May I ask, what gaps do you find in the currently available reports?

Hello @[deleted] this is an interesting case given an issue can belong to multiple sprints and there is no easy way to use JQL to filter based on the last sprint. However, you might be able to generate a sprint report just before you close the ongoing sprint by using the openSprints() JQL option…

Hi there! nice topic. I find most of my fun coding time I've spent it on coding challenges, enjoying the sometimes odd questions or problem scenarios. Most of the time spent on this I've done on codesignal and/or hackerrank.

Aw yeah!