Petter Gonçalves Atlassian Team

Hello @william_nguyen Welcome to Atlassian Community! The Control chart of the Jira application is calculated based on the time the issue remained in each status you select to be displayed in the chart. Based on that data, the control chart will display the Cycle Time (or Lead Time) of your issues and give you an overall…

Hello @Bob Sochacki Welcome to the Atlassian Community! In Jira Cloud, we have recently acquired a new functionally (From Codebarrel) that you can use to automatically create a new linked task when your Sev1 issues reach its final status, also selecting the project and fields that should be set in the newly created task.…

Hello @Ryan_Smith Welcome to the Atlassian community! Based on other persons also facing the same problem even though the steps this documentation were executed, I believe you might still have any connectors in server.xml that still need to be added with: <span>relaxedPathChars="[]|" </span>relaxedQueryChars="[]|{}^\`"<>"…

Hello @Андрій Муравльов Just like I mentioned in my last reply, you can edit the application access that each group provides under Product Access. The thing is: You must have at least one group with default access to each application in your site, so if you want to remove the mentioned group you will need to add a…

Hello @Yuliia Zhyliaieva Thank you for reaching out. The problem you are facing usually happens when your own user is not added to the project role. This is intended behavior since the system should not allow groups/roles to be added with access to Dashboard or filters when they are not related to yourself. Please, try the…

Hello @Sandra Bar Thank you for reaching out. The error you are facing usually happens when you have a third-party plugin in your Jira installation that is not compatible with the newly upgraded Jira version. That being said, I recommend you to try the steps in this documentation: * Stop JIRA * Go to your the <a…

Hello @Wendy McCurdy Welcome to the Atlassian community! Jira Classic and Next-gen are basically the same core application, however, with different complexities and customization options. Basically, Jira Classic provides you with all the features and customizations available in the application, while next-gen provide you…

Hello @Андрій Муравльов Thank you for reaching out. To properly edit a project role and check which users are added to a role by default, you can navigate to Jira Settings > System > Project roles, as you can see in the documentation below: Managing project roles To edit the name and description of a project role, locate…

Hello @Alex_VIP Thank you for reaching out. Indeed, it is not possible to restrict users to see tickets from other customers when they are added to the same organization and the issues are shared with them. In fact, that's the whole functionality of Jira Service desk organizations: Be able to share tickets with other…

Hello @karim.belhadj Thank you for reaching out. Can you please confirm to us what is the Jira version you are using? As you can see in the link below, there's a bug with Jira application on version 8.6 and above that cause all the groups under users and roles to display as "Inactive": Jira 8.6.0: All Groups are showing…

Hello @Ines Büntig Thank you for reaching out. Per your description, I understand that you want a notification to be sent to the customer together with the downgrade of his issue when BOTH conditions below are met together: 1 - The issue is in the status 'waiting for customer' for 2 days or more 2 - The SLA "Time to done"…

De nada, @Rafael Ibanhez Na verdade, sou brasileiro também. :) Tenha um ótimo final de semana e não hesite em entrar em contato caso surja alguma outra dúvida.

Hello @[deleted] Welcome to Atlassian Community! I understand that you have properly created a Checkbox field in Jira with the options Color1, color2, color3, and color4. However, the options color1 and color4 do not get flagged when you import issues using a CSV file, although you added them with the correct values. Is…

Hello @Derek Metz Thank you for reaching out. Unfortunately, it is not possible to prevent/select specific fields from being cloned when using the Jira Clone functionality. We clearly understand how useful this functionality would be, so we created the following feature request to get this feature implemented in Jira Cloud…

Hello @Lisa Tritt Thank you for reaching out. Indeed, it is not possible to change the fields displayed when creating linked issues. We understand how useful this functionality would be, so we created the following feature request: - As an administrator, I want to be able to change the create linked issue screen Feel free…

Hello @WasimBuden Thank you for reaching out. I understand you need to create an SLA that would be reset every time your team sends a comment/update to the customer, starting the counter again. Is that correct? Indeed, the own internal Atlassian support portal works with this possibility, where we use a status change to…

Hello @Rafael Ibanhez Thank you for reaching out! I understand that you need to send a notification e-mail when an issue is transitioned to a specific status containing all the issue keys of the related linked issues, using Automation for Jira app. Is that correct? Basically, you have two kinds of links between issues:…

Hello @Prasad Andrews Thank you for reaching out. Unfortunately, it is not possible to restrict users to add new labels. In fact, the ability to create any new values by anyone is the characteristic that differentiates labels from other field types. That being said, we completely understand the value it would have in some…

Hello @[deleted] Jira software projects (Business and Software) can also be configured to create issues from e-mail, although they use a different e-mail handler. To know how you can create issues from e-mail in Jira Core and software projects (Both classic and next-gen), please take a look in the documentation below:…

Hello @Jack Woehr Indeed, the only way would be to use that same structure containing the issue key in the subject of the e-mail to address it to the Ticket. If you have any questions or ideas on how we can do it better, please feel free to provide us with this feedback so we can consider it with our Development team.

Hello @Assaf.Shouval Welcome to Atlassian Community! Can you please confirm if you are using a Next-gen or Classic Kanban board and how much time your boards are taking to get fully loaded? If you are using a Next-gen Kanban board, I believe you might be facing the following bug: Performance degradation of Next-gen boards…

Hello @Laura_Morgan Thank you for reaching out. To properly deactivate the ability to log work in issues when they achieve a determined status (Done), you can use the workflow property jira.permission.work.denied, as mentioned in this documentation: - How to restrict Log Work on a specific status These would be the steps…

Hello @Jack Woehr Thank you for reaching out. There are two possible ways to forward an e-mail and add it as a Jira ticket: 1 - You can add the e-mail description as a comment to an existing ticket Using this option, only the e-mail description will be added as a comment to the existing issue. To do it, you must add the…

Hello @Roberto Leone Welcome to Atlassian Community! Per your description, I understand you created a new filter that you can not edit anymore, although you are able to access and run that filter. Can you please provide us a screenshot displaying the exact view you have when you run the filter? By default, the option to…

Hello @Rob Horan Thank you for reaching out. Unfortunately, Jira does not have an inbuilt integration that would allow you to send a meeting in outlook through an issue transition based on the value of a date & time field. In fact, we opened a feature request to implement this feature in the past, however, it was not…

Hello @totkzv Welcome to Atlassian Community! The permission to assign issues is added by the project permission scheme, where the users can select which users/groups/roles can assign issues on a per-project basis. That being said, these would be the steps to properly allow the manager2 to assign issues without the need to…

Hello @Jessica Hitchens Thank you for reaching out. Per your description, I understand you need to create a swimlane in your board that will display all the defects that are: 1 - Linked to Stories 2 - Is added with a fix version (Release) If I understood your request correctly, you can configure a JQL to be used as a…

I'm glad your problem is solved, @Dave Menconi Indeed, the incoherency that is eventually caused by the movement of the columns and issues in Next-gen can be fixed by enforcing a re-index with the moving of the right-most column out and back to the same position. Have a nice day and let us know in case you have any other…

Hello @Hannah_Avellaneda Could you please provide us more details about what you are trying to achieve exactly? The instructions I provided above are not related to boards, but to the projects in Jira. Can you please provide us some screenshots of what you are trying to achieve and what is the problem you are facing?

Hello @carina.norelid Thank you for reaching out and welcome to Atlassian Community. About this behavior: By doing so the burndown chart doesn't seem to be correct... It takes both the Story estimation and the subtask estimation into account, so remaining time estimate doubles (which isn't correct). That's not the behavior…