Walter Buggenhout Community Champion

Hi @Jack Yang, No, you can't. A Jira project only has one field configuration. However, it is very likely that you will be able to fix what you are trying to achieve in a different way, using screen configuration and workflow settings. If you want to hide certain fields for a specific issue type, you can simply create…

Hi @Nico and welcome to the Community! How do you define "marked as done"? And what do you mean by "the backlog screen". Most likely, there is something wrong with the mapping of workflow statuses to the columns of your board. The backlog column should only contain one status (i.e. the status that represents your backlog).…

Hi @Barış Özer, I am currently running a test myself on a test site. There's a number of things that should be in place here: * First of all, the configuration of your SLA should be correct. I do not know what your workflow looks like, but from the screenshot you shared, it seems as if your SLA starts when an issue enters…

Hi @Barış Özer, I am not sure how you can say it did't work after trying for 5 minutes. This trigger fires for tickets based on the SLA timer that is running. If a ticket reaches the 24 hour mark before the end of the SLA, it should activate the rule. If you don't have any tickets that match the exact trigger, nothing will…

Hi @Barış Özer, If I understand your use case correctly, you are trying to send a email 24 hours before the SLA (of 48 hours) expires. To do so, in the SLA threshold breached trigger select the second option: will breach in the next 24 hours. Your current configuration will try to send the email 24 hours after the 48 hour…

Hi @Hemnath.N, As the message says: have a look into the logs what is going on there. It may be a good idea to reach out to Atlassian Support with your findings. They may ask you to provide a support zip to diagnose the issue. For instructions on how to create it, see this support article.

Hi @Hemnath.N and welcome to the Community! The Jira Cloud Migration Assistant (JCMA) is a marketplace app. If it is installed on your Jira instance, you should be able to find it under the Import and Export section of system settings. To make sure it's (not) there, just type 'gg' and then in the dialog that appears…

Hi @Jessie Li, Most likely, there is no json required to set field values. You can copy values from the trigger issue just like this: Just select the fields you want to fill out. With the ... link next to each field select copy from and then update the selected option to copy ... from trigger issue as you can see in the…

Hi @Bar Abergel, As you have noticed, filtering dynamically based on dynamic time ranges is not a walk in the park. You can make your querying a lot easier if you add a custom field to indicate if an issue was created within or outside SLA working hours. Using automation, you can then simply set the proper value in that…

Hi @Omar Mohamed Fathi, Adding to @Gaurav: indeed, Assets is only available as part of the premium or enterprise plan. Assets Discovery is a network scanner that is capable of discovering hardware and software in your local network and pulling details into the Assets app. It is a very useful addition to Assets, and you can…

As long as it is ticket progress that you are referring to, tickets have a customer facing status, which represents the stage in the ticket workflow as you want it to be seen by customers. However, that is the status the reporter can see as well from the my requests page in the customer portal. So no need/use to add the…

That is unfortunately a misconception, @Alex S. A request participant does not have any additional permissions in comparison to the reporter. All this is for, is to add a backup person for the ticket to follow and participate in comments. If a user needs to see the full details of a ticket (i.e. all the internal…

Hi @Alsaaa Bano and welcome to the Community! You can find detailed steps on how to configure approvals in Jira Service Management from this support article. That link is to an overview article, but additional steps are available from links on the right hand side navigation in there. You may be interested more specifically…

Hi @meliodas16, Yes, it is expected behaviour. The moment your SLA is considered breached (and when a ticket appears on the report) is when the SLA timer stops. This was on December 11th. The detail displayed in your first screenshot shows the time when your issue should have been resolved (or replied to, or anything else…

Hi @Abby Kiesling, I don't know how you have created a form in a Jira Product Discovery project before. I cannot remember having seen the capability there. Forms are a feature of Jira Work Management, which is a different product having its own feature set. While Jira also offers the issue collector, that is only available…

Hi @Josh Henry Regondola and welcome to the Community! Since you provided payment details, I assume you are not on a free plan. Having said that, I recommend you reach out to support directly via https://support.atlassian.com/contact/#/ The Community forum here is mainly driven by volunteer people who cannot access your…

Returned on Friday with yet another bag full of great conversations, memories and a ton of things to do in the coming months. One of the best takeaways for me from this event is how the relationship between Atlassian and the solution partner ecosystem is evolving into true and close collaboration (again) to provide a world…

Hi @Marcin Jaworski, You can take a look at the Version report where scope change is indicated over time, as well as the Sprint report, where details are available at sprint level. Hope this helps!

Hi @Madakannu Prabhu and welcome to the Community! Charts - such as the burndown chart - are linked to a board and not a project. If you create a board based on the data coming from the multiple projects, I would suspect the reports should look fine too. Your board filter (accessible from board settings > General) should…

Great to see you there, @Dirk Ronsmans 🤗 Drove 300 kms today across a large part of Belgium and loved it. Great interaction, good conversations and quite a good crowd at the same Belgian ACE: B-ACE-27: The State of Teams Roadshow with Mark Cruth from Atlassian

Hi @Lauren Kirt, Advanced Roadmaps (as does Jira in its entirety) visualises an entire plan from issues. What you would need to visualise the start and end dates of your project, is an issue that represents the project itself. That means you would have to extend the existing issue hierarchy in Jira above the Epics…

Hi @DINESH, SLA configuration is rather a feature of Jira Service Management and better supported there, in the sense that it's easier there to use the SLA timer to select issues that are ablout to breach. In Jira Software, you could mainly use the due date (or another date custom field) as a target for issues to be…

Hi @Andy Atkinson, Sub-tasks are a specific issue type, in the Jira hierarchy not supposed to be below an Epic, but one level deeper: below stories / tasks / bugs (which are called standard issue types). I suspect that is why the check box does not have any effect on Epics. Hope this helps! 

Hi @Mavis Mazhura, Just click the Disrupt Cards link in Monica's question above. That is a direct download link. Or download them from the What you need section in the Playbook play itself. 

Hi @Jimmy Trivedi, In your Community profile notification settings , there's a check that says "Automatically watch everything I participate in" and several checks that explicitly turn off certain notifications. Most likely, it is one / a combination of the changes you made to your notification settings that is causing…

Hi @Alice Winston and welcome to the Community! I am not really sure if I understand the scope of your question. But when I try to give you some guidance: Confluence and Jira serve different goals: Jira is where the actual work is tracked, while Confluence is where your documentation / collaboration lives. Depending on the…

Hi @adaraz.untrif and welcome to the Community! There is a sample rule in the automation rule that does exactly what you describe. Hope this helps!

I will be attending the 30 Nov Belgian ACE on the State of Teams report with Mark Cruth from Atlassian. Also very much looking forward to meeting @Peter Van de Voorde there, as its been a while since the last time in person 🤗

Hi @Jibin George and welcome to the Community! The built-in feature that you can use in Jira are the versions, which you probably are familiar with. Jira Software comes with 2 out of the box custom fields that help you manage versions on issues: fix versions and affects versions. The first one helps you indicate the…

Hi @Phil, A(n) (agile) team is a group of people that works together on shared goals / a shared backlog, right? In some cases, a team is dedicated to a single project for a long time, in which case team / project planning is basically the same thing. No issue there. Complexity starts when teams work across multiple…