Walter Buggenhout Community Champion

Hi @Mahant Madiwal , JQL queries in Jira search for issues, not releases. However, if you search for all issues (that would just be an empty search, with no criteria at all), you can use the output to visualise those issues per release. You may e.g. use a pie chart gadget where you use fix version for the pieces of your…

As John is suggesting, could you check what the status of your issues is immediately after they are created? In the example you shared (CRF-6) - what was the issue status when it was just created?

Hi @Bill Bracken, Welcome to the Community! It should be possible to update your estimate later on. The key is to have the Time Tracking field available on the edit screen of the issue type you want to update it on. To check if this is the case, navigate to Project settings > Screens and locate the edit screen associated…

Hi @Hiruni Madola, It seems as though the full functionality of scroll versions is too complex to implement in cloud, but it seems that scroll documents does offer certain versioning functionalities in the cloud. More details are already in this related question. It is probably best to speak to the people of k15t directly…

Hi @Lars Böhnke , I see this is quite an old question already. There is a good chance that you already found a solution and if so: cheers to that! I also noticed your question had over 1.110 views and no answer. So I thought it may still be useful to do something about that. When you create a project poster from…

What you found difficult to learn about Insight? * Inbound and outbound references * referencing and filtering custom fields * importing data from csv * IQL, especially when referencing attributes What you would like to learn more about? * The future of Insight in Jira Software (we set up several CRM like cases and product…

Hi @jfriedberg , Have a look at how to configure both global and project customer permissions in this support article. It is those permission settings combined that impact access to your service desk. From the article:

Hi @Vijay Kumar, The release burndown chart uses the information of past sprints in order to do forecasting towards the future. So that means you will have to be 3 sprints in before you will start to see forecasts appear. This makes sense, since the burndown is related to your team's velocity. It is best to have data…

Hi @[deleted], The documentation is not outspokenly clear on the topic. In the server version, there is an explicit mention that your stakeholders need view plan permissions in order to see the shared roadmap. The below statement from the cloud documentation at least suggests that this permission is not necessary: You…

Hi @Vijay Kumar, There is a good chance that the Story Point field is simply not on the edit screen of stories. This is definitely not a limitation of Jira, but a configuration issue. That may be by accident or a process decision. In your project settings, navigate to screens, and find out which screens are being used for…

Your JSM project already have a permission scheme where - by default - the permissions to collaborate internally are granted to the Service Desk Team role. Assigning your internal people to that role will grant them the permissions they need. One caveat though - which is why I mentioned Jira Software. Your users need a…

Yes, definitely. You basically set up 5 different projects. In each project you grant access to your users in Project Settings / People by assigning them to the Service Desk Team role. For more details, check out related documentation for your internal users and (for the sake of completeness) documentation on customer…

Hi @eSolutions Customer Support, There is no option to trigger this through JQL. You could set up an SLA for this, as it takes your support calendar into account. Automation then offers you the SLA Threshold Breached trigger to e.g. send an email after 3 and 7 days and close the issue after 10 days. 

Hi @Cathy, Just to answer to your question first and foremost: project category does not impact access to projects in any way. It is mainly useful to: * Keep your projects organised and easy to identify as similar projects * Make it easy to search for issues across those similar projects To specify the last statement: you…

Our consultancy has a daily standup, which is entirely remote over zoom. As most of us are working on their own projects, we focus mostly on keeping everyone in the loop on what everyone is at. That is mostly an informative part. The key part is the I'm stuck and I could use some help here bit, which is key to pull in…

An update on my own comment: I noticed there is a new category of information with videos, next to articles in e.g. the Jira collection. However, watching videos there doesn't seem to trigger either.

Hi @Rhys Christian Could you look into the possibility to set default values for the team field in Jira Cloud? As a crucial part of building the roadmap, work must be associated with a team. There is no better moment to do this as when an issue gets created. I know that - when using shared teams - the Team custom field can…

Some new challenges popped up today, I saw. I tried out the video viewer challenge by watching a video on advanced roadmaps, over on this page: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/3-short-videos-to-help-you-get-started-with-Advanced-Roadmaps/ba-p/1439078 However, the challenge is not being awarded.

Hi @Jane Puleston Jones , In case you are looking for the Epics panel in your kanban board, you need to enable Kanban backlog first and then enable the Epics panel there. This article describes how to do both. Look for the section about Enabling the Kanban backlog.

Hi @Pierre Legrand (Contractor), You could use bulk update for this. Select the items you want to update simultaneously using the check boxes in front of them. Then, through bulk actions update the team for the whole set: The automatic cascade in the old Portfolio was definitely quicker than this, but it is a workaround…

You're welcome @Samuel Justus. Glad we managed to find the cause! Would you mind marking the answer as accepted (assuming that all is fine now)? That is useful for users running into similar problems! Thx and keep up the good work! 

Hi @Monique vdB, I had noticed the message coming by in the slack channel too. Thx for the update! 

Hi @Samuel Justus, Now we're talking ;-) I see that - despite your board is located in the Team Penguin project - both projects that you assigned the new filter to are simply not in your board filter. From the screenshot of the workflow, I can see that the workflow is being used in 2 projects: Team Penguin and Striker.…

Your customer needs product access to Jira Software (and - as such - a license) before he can be granted access to your projects. You'll need to set up in your site Administration / User Management / product access for that user.

Hi @Madineni, Your JQL statement doesn't look too far off. May I suggest a different approach and/or an extension to your automation instead? A first option would be to extend your automation so you close the ticket automatically after 5 days. In that case, make sure your client does have the option to reopen the ticket in…

Hi @Indira Gandhi Kannan, First of all, in your filter results hide the columns you don't want to extract from the columns button at the top right of your search results: Then, when you export choose the option Export Excel csv (current fields)

There is not much more you can do in terms of access. Maybe it is related to browser caching on the part of this one user. You could ask him/her to clear the browser history (or log out and back in again)

About the vacation part: the tool does not support you there. The sprint is a commitment of the set of issues you commit to as a team for a certain time box (of usually just a couple of weeks, right). The tool is there to visualise the result of your underlying sprint planning process, where you sit together as a team and…

Sure, Just be aware that the more sprints you create up front, the more hassle it will be to assign issues from the backlog into the correct sprint. In sprint planning, that will usually be the next sprint (maybe 2 or 3 maximum ahead of time). And I know from experience that no living being is capable of correctly planning…

Have you checked if there aren't any filters currently active? A quick filter e.g or an epic or version that has been selected?