Petter Gonçalves Atlassian Team

Hello Srikanth, Welcome to Atlassian Community! Unfortunately, there is no official REST API call to update Customer requests on JIRA yet. We have a feature request to implement it here: - Ability to update Customer request via REST API Feel free to vote and watch the suggestion to increase its priority and also receive…

Hello Nina, Unfortunately, JIRA Next-gen does not support any kind of workflow customizations, as transition functionalities (Post functions, Validators, Condition or Screens). In fact, the Next-gen project template was created with the intent to provide a simpler and limited option for those customers who felt overwhelmed…

Hello Sami, Welcome to Atlassian Community! To automatically assign a ticket to a specific user or change any fields when an issue is transitioned, you can use the Board rules of Next-gen projects. These are the steps: - Navigate to your next-gen project board - Click on the three dots icon > Manage Rules - Select the…

Hello Joe, Welcome to Atlassian community! Checking other support requests opened with the same error, it is possible that no default groups that give any product access have been added to the mentioned user. Please, try to add the user to the default product access of your JIRA Application as mentioned in this…

Hello Andrew, Basically, the People Section under Project Settings defines the users added to the Project Roles of that specific Project. To see and define what each Project Role can perform/access in a project, you can check the Permissions section under Project Settings. That been said, it will depend on how your People…

Hello Jordan, In order to properly notify a specific user when an incident is created, you just need to add him into the Create issue notification under project settings > Notifications. To add him as the assignee when the issue is created, you can set him as the default assignee under project settings > Details. About…

Hello Kaushik, Basically, the integration between JIRA And ServiceNow can be performed by WebHooks, using the articles below: * https://developer.atlassian.com/jiradev/jira-apis/webhooks (documentation for JIRA Server) * https://confluence.atlassian.com/adminjiracloud/managing-webhooks-776636231.html (doc. for JIRA Cloud)…

Hello Andrew, I think I have two suggestions that might help you get a better visibility of what is falling behind your scrum projects: 1 - You can create a single global board to track all the items you want across projects Basically, you can create a new board to track all the items of your Scrum projects, using the JQL…

Hello Adrian, Welcome to Atlassian community. The functionality to automatically transition sub-tasks when its parent is transitioned cannot be achieved using only JIRA. We have a feature request about this matter here: - Auto transition Sub-Task when the parent issue transitioned in a workflow Feel free to vote and watch…

You are welcome, Natalia! Have a nice week ahead. :)

You are welcome, Steven! Have a nice week ahead and let me know if you need any help configuring the classic board. :)

You are welcome, Jordan. Have a nice week ahead.

Hello Steven, Welcome to Atlassian community. I understand that you would like to prioritize your \Epics in a next-gen Kanban board, Splitting them in swimlanes organized by labels that will define their priority. Is it correct? Next-gen projects are simpler and limited templates built for those customers who needed a…

Hello Shail, I assume the support type issue you are talking about is a custom issue type of your JIRA instance, is it correct? The first thing that came to my mind that could be causing this behavior is that Epics can only be mapped to Standard issue types but not Sub-task issue types. Could you please navigate to JIRA…

Hello Allan, Welcome to Atlassian community! The ability to add customized Issuekey number was requested a while ago to be implemented on JIRA, however, since it is ordered in the same way as the database id, this action proved to be hard to implement cause the database Id is related to the issuekey. It would require a…

Hello Troy, Unfortunately, some features of JIRA Next-gen are not supported in the Automation for JIRA app right now, including Sprint pickers. You check any updates and the progress of Codebarrel developers to implement this feature in their bug report below: - Support nextgen sprint options in sprint field picker…

Hello Heidy, Welcome to Atlassian Community! The way you configure the due date field depends if you are using a next-gen project or a Classic project of JIRA. 1 - Here are the steps to properly configure the due date field to your bug tickets in a Classic project: - Navigate to your project > Project Settings > Screens -…

Hello Steve, Welcome to Atlassian Community. The way to create application links will depend if you are using JIRA Cloud or Server and what is the version of your JIRA if you are using JIRA Server. Supposing you are using JIRA Cloud or the new versions of JIRA Server, you can perform the steps below: * Log in to Jira as a…

Hello Sadia, Welcome to Atlassian community. Indeed, there are some old bugs and settings that can be causing this issue. In order to better troubleshoot the problem and reduce the possibilities, please provide us some more information and try to perform the following steps: 1 - Are you using JIRA Server or Cloud? If you…

Hello Nick, Sorry to hear the workaround provided with the Old issue view does not help. Could you please provide us more details about your scenario so we can provide you any other options? In other words, I would like to know what features you are using in the New issue view that do not have/don't work as you expect in…

Hello Erik, The field that informs the step of the issue in the workflow is the Status field, which is also displayed in the new issue view: That been said, I believe you are talking about the (View workflow) link that appears on the right side of the status when you are using the Old issue view, is that correct? If that's…

You are welcome, Stephen. Let me know if you need any help to set any of the suggested options.

Hello Stephen, Welcome to Atlassian community! Using only JIRA application, there are some options you can perform to achieve something similar to issue templates: 1 - Create an Epic + Child issues to be used as a template. Once you need to create new Epic and Child issues, navigate to the template Epic and the related…

Hello Jordan, Welcome to Atlassian community! I understand that you would like to allow all the customers from a specific organization to access/comment on all tickets created, is it correct? This functionality can be achieved by performing the following steps: 1 - Navigate your service Desk projects > Customers > Add all…

Hello Ben, Welcome to Atlassian community. Unfortunately, CRM for JIRA Cloud app only supports the integration with Salesforce, Microsoft Dynamics, and Hubspot. That being said, I found two third-party applications that provide this kind of Universal Connector for Both JIRA and Copper, although they are not supported by…

Hello Nick, Welcome to Atlassian community! The summing of sub-task estimation can be achieved only in the Old issue View, where you have a flag to include sub-task estimation in the Tim Tracking field of the Parent Story. We have a feature request to implement it in the New issue view here: - New JIRA Issue View don't…

Thank you for letting us know it's solved, Camille.

Hello Leyla, Actually, the mentioned behavior is intended when you don't have the assignee field in the Screens, as you can see in the bug reported. Sorry, but I think I didn't understand what did you mean by a permanent solution. Adding the assignee to the issue screen is still lacking your system in any way?

You are welcome, Vinay. :)

Hello Koteswararao, Next-gen projects use a different set of functionalities that works in a different way, including the epic-story relationship, where no Epic Name Or Epic Link is configured. That been said, the Epic-Story relationship is not migrated from Next-gen to Classic projects and must be configured again once…