Walter Buggenhout Community Champion

Hi @[deleted], I am not quite sure if you are looking into version control of either configuration or the data on your boards and roadmap. In terms of configuration there is indeed no versioning or change control in place. There is a decent amount of audit logging in place in Jira, but that does not cover changes to boards…

Hi @Jake Laack, If you mention the Atlassian docs on services, I assume you refer to the pages listed here: Manage your services. It is worth looking into as it explains more about the capabilities of services. If you are on the free plan, services are just a catalog in your instance. And then I totally get you when you…

Oooh, that's one I can't leave unanswered 😃 For some of the folks that go back some time this isn't new, but back in 2004 I accidentally got involved in the BBQ World Championship in Germany. I was a participant at a cooking course and we decided to participate in the competition with a couple of volunteers from our group.…

No @Alexander Boden, the basic roadmap does not extend above Epics. If you need that, you would be looking into advanced roadmaps (a feature of the premium plan) or marketplace apps like eg structure (ALM Works). 

Hi @Kshitij Yelkar, This is indeed a known issue. It is currently being worked on and apparently seen as a priority by Atlassian to bring this functionality back. You can track when it gets released through JRACLOUD-71827.

In company managed projects, you add issue types to your project by adding them to the issue type scheme of your project. You can find that quite similarly through Project Settings > Issue types. 

Hi @Alexander Boden, That is definitely possible. In this example, I added an invoice to the roadmap: You need to add the additional issue type to your project. In this example my project is team managed. Through Project Settings > Issue Types you can add additional issue types to your project. Once they are defined in…

Yes, I understand. Usually that is what you would want, as it makes sure that a same issue type is using the same screens (and custom fields) across your entire Jira instance. That helps to create a common understanding across your organisation of a story, a bug or a task. But if that is not what you want, identify those…

Hi @Valerie Pierre, You'd rather be looking at automation to do this. You could set up a rule that: * is being triggered by an issue being completed; * for all linked issues with a specific link type * send a notification or add a comment To get you started, have a look at this rule from the template library The When part…

Hi @Valery Delannoy, Only if you were to set up anonymous access to it, as described in this support article. But that would mean you expose your data to the entire internet. If you want to give access to specific users, they need a license. Hope this helps!

Hi @Corinne Deflaux, From what you explain, it seems that you have quite a lot of users. It might be an idea to export your users so you get a decent list you can manually go through in Excel. You should be able to export a list of user from admin.atlassian.com and navigate to User Management. There is a blue button to…

As I mentioned in my first reply, @K. Yvonne Lucas, the obvious choice is the built-in advanced roadmap from the premium plan. For more information, see this introductory post.

Hey @K. Yvonne Lucas, There are tons of apps out there for project planning, roadmapping, ... They come in different flavours and each has its own characteristics that make it stand out in some way or the other. Have a look at this list to get you started. 

Hi @Michael Schroff, You can definitely come a long way with the two dimensional issue statistics gadget on a Jira dashboard (the article I linked is from Data Center, but the gadget is available on cloud as well). How you drill into your data obviously relates to how you categorise / organise your issues. Let's just…

Hi @Muhammad Akram Sharifi, If you associated your new screen scheme to an existing issue type screen scheme, then you have just added your freshly created screen scheme to all the projects the issue type screen scheme was already associated with. And probably that is 2 projects. If you click on the link that says the…

No indeed, @Drew Nedderman. And that is because he does not have access by not having a license. I you would expect to find a user in a space with anonymous access enabled, you should also be able to find me in there, for example. Or anyone else that has an email address or an Atlassian account somewhere in the world. That…

Hi @Drew Nedderman, Essentially these users don't have access, except to spaces: * you granted anonymous access to; * or that can be accessed through Jira Service Desk as a knowledge base space. So even when certain groups of users have access to a space, if your users don't have a license and those spaces cannot be…

Hi @K. Yvonne Lucas, No it can't. The classic roadmap is designed to show issue from a single project only, as you can clearly see from this experiment: If you want a roadmap across multiple projects, advanced roadmaps from the premium plan could be the answer. Hope this helps! 

As soon as you have your automation is in place and automatically changes the status of your ticket, you can start and pause your SLA timer just from the status transitions. e.g.: start when ticket is created, stop when ticket is resolved and pause when the ticket is in status waiting for customer.

The user's role should be Service Desk Customer. You don't need to do anything in your workflow, but you would normally have to set up an automation rule to automatically transition your ticket from Waiting for Customer to In progress when a customer comments. Legacy automation had a built-in automation rule for that,…

Hi @Hoc, When reading between the lines of this support article, that should be possible: For more information about Atlassian Access and managing your organization, see also this article. Hope this helps!

Hi @Riki YAMASHITA, We have noticed in testing that results may be inconsistent when you have multiple roles in your service desk project. When you are both an agent and a customer in your service desk, the evaluation of the condition that you are posting as a customer does not trigger the rule correctly. If that is what…

Hi @Patan Irfan Ali Khan, If tickets are moving back from a closed / resolved status, it is because your workflows allow them to. I suppose tickets are not automagically moving back, but because either users or an automation rule is causing that to happen. You'll have some digging to do into your configurations, most…

Hi @Alin Faur, When you migrate from Jira Server to cloud using the Jira Cloud Migration Assistant , only boards associated with a single project will be migrated. Cross project boards cannot be migrated at all and must be recreated separately in Cloud. Through a manual import (csv as you describe), there is no way to…

Hi @jordi subirats, You can find the available procedures for having your domain name changed in this support article. Congratulations on the rebrand!

Hi @Andile Luvuno, A good way to deal with this, is through a filter subscription. The following filters may give you a list of issues with due date tomorrow or overdue: Project = X AND due >= StartOfDay(1) AND due <= EndOfDay(1) Project = X AND due < StartOfDay AND Resolution = Unresolved With a group filter subscription…

Maybe an interesting addition to that: should you be unsure as to certain people are receiving notifications on a certain event, you can use the notification helper to verify that. It allows you to test if a certain user should be getting a notification when a specific event occurs for an issue.

Hi @Gajanan Sasane, As I explained above: if the notification scheme of your project is configured so that notifications are sent to All Watchers, and your watchers are licensed Jira users, then yes. Also note that your notification scheme contains many different events to send notifications for (issue created, issue…

Hi @witold.proszynski, You should be able to access the products in your site from admin.atlassian.com and selecting "manage subscriptions" from the left hand side navigation. After adding a product, you can change the plan of each product in your site. after clicking Change for the product of your choice, you can select…

Hi @Anthony Dobles, In order to do this, your existing kanban board must be a board in a company-managed project. If that is the case, navigate to the board settings of your kanban board. On the general tab, locate the filter of the board and click Edit filter query. Modify the filter to include not only the tickets from…