Petter Gonçalves Atlassian Team

Hello @[deleted] Thank you for reaching out. Unfortunately, there's a bug in the syntax of JIRA REST API that blocks the ability to add multiple watchers with a single REST API call: REST API add watcher (POST) request is not a valid JSON syntax Feel free to vote and watch the bug to receive notifications about the fixing…

Hello @Efoe Adjakly, Welcome to Atlassian Community! The star symbol in those issues (*) means that the issues were added after the beginning of the sprint, as described in the "Understanding the Sprint report" section of this documentation: Issues added after the sprint starts are indicated with an asterisk. This feature…

Hello Andrew, Thank you for your answer. For now, I would try the following tests: 1 - The ideal scenario would be to import the XML to an instance in the same version. That being said: - Try to import the XML file in a JIRA instance 8.1.0, - Upgrade it to 8.3.3 - Export the file again and try to import it in your current…

Hello @SHANAVASH MOHAMED Thank you for your answer. Since you are using Story points to estimate your issues, The following scenarios might be causing the issue: 1 - You select the wrong Story point field to estimate your issues. Let me explain it better: Currently, you have both Story Points and Story Point…

Thank you very much for letting us know this, @winter wong Have a nice day! If there's anything else we can help with, please let us know. :)

You are welcome Rebecca, Thank you for providing these details. About your specific concerns: 1 - Indeed, JIRA has a time tracking feature which tracks your issues based in three fields: Original Time estimate (Initial estimation), Time spent (time logged to your issues) and remaining time (Initial estimation less the time…

Hello David, Thank you for reaching out. The documentation below provides you with all the instructions you need to connect Okta and Atlassian Cloud and how to provision users automatically using the Atlassian Access application: - Configure user provisioning with Okta Basically, once you've checked the prerequisites to…

Hello Marcus, Thank you for reaching out. Please, allow me to bring you some concepts so we can better understand your issue and confirm that we are on the same page: The bug you mentioned was reporting specifically that non-agents users were not able to view the work logs panel of Tempo plugin. This bug was fixed in…

Hello @Subbu Thank you for reaching out. Yes, the third-party vendor Scribesoft developed a connector to integrate Tibco and JIRA for both Cloud and Server platforms, supporting source and target operations for common Jira objects, including issues, comments, and attachments. You can check more details about the connector…

Hello Arjan, Thank you for reaching out! Unfortunately, the automation provided by JIRA Service Desk cannot link created issues to all issues with the same value for a custom field, since the linked issues field is not searchable with JQL in the automation. That being said, I know two possible alternatives for you: 1 - you…

Hello Andrea, Welcome to Atlassian Community! Unfortunately, it's not possible to configure customized hierarchical levels in your JIRA site. The only hierarchy available is: Epics -> Standard Issues (Tasks, bugs, stories, etc) -> Sub-tasks We have some feature requests to allow the creation of more hierarchy levels in…

Hello Andrew, Welcome to Atlassian Community! Please, follow the steps below in order to properly troubleshoot the problem and better understand the error returned when trying to import a new project in your JIRA instance: 1 - About the XML file you are trying to import, was it generated from another Jira instance or…

Hello Helen, Welcome to Atlassian Community! I believe you are trying to automatically update a field with a specific value when the issue is transitioned, by using a post function with a SIL script provided by Power Scripts App. Is that correct? The Sil code for that will depend on which fields you are trying to update,…

Hello Tejas, Thank you very much for your details. Analyzing your logs, it seems that you are facing an error similar to the one commented in this thread: - No Custom Field For customfield in Bar Chart plugin That being said, it seems that the customfield_11202 is not configured with a valid entry, causing the issue you…

Hello Tejas, Thank you very much for your details. Analyzing your logs, it seems that you are facing an error similar to the one commented in this thread: - No Custom Field For customfield in Bar Chart plugin That being said, it seems that the customfield_11202 is not configured with a valid entry, causing the issue you…

Hello @PM_Rita Sorry, but I think I didn't understand if you are still facing the problem. If you are still facing it, can you please share with us the CSV file you are trying to import? Please, make sure you removed all the sensitive data from that. Also, are you trying to import the issues to a Classic or a Next-gen…

Hello Kimi, Thank you for reaching out. I believe there is not a right/wrong way to configure your issue types hierarchy in the current scenario you have. You could use the parent-child issue link or the conventional link between the standard-issue type. Also, there's the possibility to use Epic issues as the top parent,…

Hello Danilo, Welcome to Atlassian Community! The approval functionality is a feature applicable only for JIRA Service Desk projects. That being said, in order to display the approver option for your workflow statuses, you must first map your workflow to the workflow scheme of your project and select it for the issue types…

Hello Praveen, Thank you for reaching out. I understand that you would like to make sure the users in Jira will select Done in the "epic status" when marking the Epic as done. Is it correct? Unfortunately, there is no way to remove the status of your "Epic Status" field since it is a locked field (see JRACLOUD-64188 ),…

Hello @Cast_Informatica_S_A_ Thank you for reaching out. analyzing the errors returned in your integrity checker, I believe there are data integrity issues in your database due to a null issue key in your JIRA, however, it's hard to troubleshoot what might be causing it. I suggest you check in the documentation below if…

Hello Filipe, Welcome to Atlassian Community! Unfortunately, it is not possible at this moment to hide done epics from the Epic Link drop-down in the child issues, however, we understand how this feature would be useful depending on how you are using JIRA. That being said, we created a feature request to add this…

Hello Kevin, Thank you for reaching out. I understand that your select list (Single choice) is not properly displaying its options in the correct same order as your web application. Is that correct? Indeed, we have a bug reported about custom field order in JIRA mobile (see JRACLOUD-71237), however, the same is not…

Hello Ronald, Thank you for reaching out. To restrict users from creating Next-gen projects, you just need to remove them from the groups added in the Create next-gen projects Global permission or remove the groups from the permission itself. These would be the steps: - Navigate to JIRA Settings > System > Global…

Hello Dani, Indeed, the second step I provided would be to create transitions to each status one at a time and then click on "reuse transition" under the create transition pop-up to do the same for the other two status. Sorry that I didn't make it more clear. I understand that this step would be a little cumbersome to be…

You are welcome, Jan. Have a nice day!

Hello @Dani Kaplan Thank you for reaching out. The easiest way to allow issues in those three statuses to transition to any status and vice-versa would be by: - Navigate to your Workflows > Click to edit it - Click on each of the three statuses and flag the option Allow all statuses to transition to this one: - Click to…

Hello Daphne, Welcome to Atlassian Community! About your questions: How do I customize Labels in a global setting so the items I add will be available for different projects? Once you create a new label by clicking in any issue, that label will be available to be selected for every single project in your JIRA Site, you…

Hello Brad, Thank you for reaching out. We completely understand your requirement to have a JQL query to display issues created in a specific time span of the day during a specific time range, however, I'm afraid there is not a function to return this kind of information with JIRA JQL. Since we understand this would be a…

Hello @Reto Schläpfer Sorry to hear you are facing this problem. Indeed, the Global Processor Puller of JIRA Service desk will reject all e-mails where the Auto-Submitted header has a value different from "no", as mentioned in this documentation. Today, we don't have a way to change that setting in JIRA SD, however, we…

Hello Peter, Thank you for reaching out. Indeed, we completely understand how practical and useful it would be if you had the functionality to embed external images inline the fields of JIRA issues. That being said, we have created the following feature request to implement that ability: - Ability to embed external images…