Walter Buggenhout Community Champion

Hi @lisa, Those are both questions you could try to cover with Automation. Have a look at the Template library to learn more about the possibilities! 

Hi @lisa, Ordering the tickets is indeed done using drag and drop. It updates the ranking of you tickets and keeps them in the order you decide they should be in. I think your board currently has swimlanes by stories, which is why you have all the subtasks visible and grouped underneath their parent stories, You can change…

Hi @Cecilia Chan, I'm not sure if you have defined releases yet for next year. But if you haven't, I'd recommend you do so and assign the 2021 work for your initiative to at least one (or more) quarterly / milestone based / MVP releases. By specifying the start date of the first release as a fixed date (e.g. 04/01/2021),…

Hi @Gleb Kartashov If you were to run the same query again now, would that same issue still show in your search results? Though it's still early in the morning and I may not be very well awake yet, I don't see anything wrong with your JQL. It should return the correct results. I think there may be an indexing issue or a…

Hi @Danno, This is probably related to the new issue view that is being rolled out in Jira Cloud. Epic status is not shown on the screens. There is an open ticket to fix that in the backlog: JRACLOUD-73469. You can watch this ticket to keep an eye on when this is fixed. The recommended workaround for now is to use the old…

Hi @Jeffrey Poole, I would assume they have the issue type bug, rather than being labelled as bugs. In that case the following filter should do: Issuetype = bug navigate to Filters > advanced issue search, click switch to JQL and enter the above. If you don't specify any projects, your search will automatically search…

Hi @Craig Lashley, I think it's a better idea to create a filter subscription for that, rather than using automation. All you need for that is a JQL filter for each team/assignee (which you already seem to have). Save the filter and from the filter details specify the frequency to send the digest and the group of users to…

Bonjour @Sabine G, There is a good chance that the story points field is not available in the field context for bugs and tasks. Which would make sense, by the way, but that's a different discussion. In Jira Settings, navigate to Custom Fields and locate the Story points field. Click configure and check to see if the field…

Hi @lisa, Regarding your first question, it is not possible to see the total number of story points in an active sprint for each column separately. There is an old feature suggestion for it in the backlog, but not much movement there: JSWCLOUD-12495. In the backlog view, you should be able to see the number of story points…

Hi @Connor Gamble, Issue ranking runs across you entire Jira instance. Each issue is unique (it's only in the database once) and it has a unique ranking compared to all other issues. That means that if someone changes the ranking of an issue, that will always have impact on other places where you see that same issue. Also,…

Hi @Alexandre Caels, Le correcteur orthographique ne fait pas partie de Jira, Confluence ou des autres outils Atlassian, mais tu pourrais utiliser le correcteur inclu dans le navigateur (browser) internet. Pour plus dínfos, voyez aussi cette question pareille

Hi @Melanie Geffre, I already had a feeling that you were on such a track. I'm not an API expert, but could this old post get you going? Or this more recent one based on the same principle?

I wrote an extensive post on trust and psychological safety, but I have the impression that some of the analogies I used directed it to the spam quarantine - I hope it can be recovered from there. Anyway, my point of the post was that the bigger the blockers, the harder it gets to get them on the table. And as calling…

Hi @Hana Kučerová, Often the most positive discoveries you do often follow moments of black snow and sorrow. The best thing related directly to the Jira product this year for me was the announcement of free Data Center Community licenses. The news does not affect me personally, but we have several customers who do run…

Hi @Melanie Geffre, It all depends what you want to do with the information. If it's just a matter of finding out what values are currently in the system, just add a JQL filter to Jira like this (let's assume the custom field is called Labelfield): Labelfield is not empty Save the filter and add a gadget to a dashboard…

It would always be better to use the API's. And I am sure several scripting or configuration tools allow you to leverage those as well. Maybe this related question on Scriptrunner may shed some light, Jira CLI has support for it, ...

That was my best guess on this. Sorry it didn't fix the issue. Maybe someone else may have additional ideas about this then. Just as a recommendation for the future: do avoid direct database updates, even (and especially) if they seem like a quick fix. There's layers between your database and the application and missing a…

Hi @Varnika Bisht, Have you tried to reindex Jira? 

Hi @Vinod Ramadoss, This looks pretty much like the velocity chart, that is available as a standard report in your scrum board. If you are looking for the capability to incorporate the report in a dashboard, surprisingly enough that is not possible out of the box. There is a long standing feature suggestion for it in the…

Hi @Martin Hemi, Your observation is correct. Child tasks cannot be moved to a board individually, except if they are child issues of an Epic. Grouping your board by subtask does help to get the overview, though this only works in the active sprint view, not in the backlog.

Welcome to the community @Nikiya Simpson! As you mention being new to agile, definitely check out https://www.atlassian.com/agile as well. Apart from a great resource into agile methodologies, it has also some great tutorials where those methodologies and Jira meet each other. Combined with the tips of the other folks out…

Hi @Ravi Amar, Next gen projects don't allow you to configure working days. There is an open ticket JSWCLOUD-17773 for this you can watch and vote for, originating from this older JSWCLOUD-17331 (listing this as - although it's closed - it has a bit more background information). 

Hi @Yonatan Ben-David, You will be able to do the JCMA cleanup yourself, but that requires deleting history records from the Jira database. It is quite important to get the correct delete queries to do this. And that's what migration support should be able to help you with. 

Just as a heads up on this - we started with weekly standups now 2 weeks ago. I took the liberty to borrow the same format you presented in the thread above. And I chose to do this in a dedicated Slack channel indeed. Although we also have a daily standup, this approach has immediately given us a better insight into the…

We started with OKRs two years ago at our company. But just now starting for the very first time to really align those with the bigger picture of the organisation as a whole. In my view it's really important to have that north star view of where the organisation is headed, so at least you can have a proper guidance and…

Hi @Ganesh Babu, Seems that apart from an impressive resume you also have a nice Community track record as well already :-) - welcome to the welcome center too! 

Actually I don't like that you're running into the same issue @Alexander Pappert - just happy to see confirmation that it's apparently more of a system problem than something with my personal setup :-)

Hi @Yonatan Ben-David, A couple of things here: When you delete a project from cloud, it gets moved into the project trash. You can find it by navigating to Settings > Projects and then from the left hand side menu select Trash. Or directly through https://<your cloud site>.atlassian.net/jira/settings/projects/trash. There…

Hey @maia, I guess you will still be able to see the old board/project, but most likely without any issues on them. After migrating, they were transferred to another project. Each issue has a unique number that identifies it. That's the issue key. I would guess the issues in your all project were all numbered PRACTI-1,…

Bingo! Really creative, this :-)