Petter Gonçalves Atlassian Team

Hello Joe, Thank you for reaching out. The "Not set" label you are seeing there is related to the Resolution field of the issue, which is incorrectly configured in your open issue. Allow me to further explain it: The resolution field is a different type of field. Basically, it works in a boolean syntax with JIRA issues…

Thank you again for this information, @eford I have contacted our Service Desk support team to prioritize your ticket, so they should be contacting you soon to take a closer look at the issue and properly troubleshoot it. Again, thank you a lot for your patience and detailed answers.

You are welcome, Henrik! Please, let us know if you face any blockers or if it worked as you expected.

Hello Arjan, Thank you for your details about how you were able to achieve your needs. That automation rule you create will absolutely help other customers looking for the same feature! Also, I'm glad to know I was able to help. Have a nice weekend!

Hello @Saumya Jain Thank you a lot for your detailed answer and patience. Indeed, I understood that your end customers (From different locations) usually do not create tickets in your support portal directly, but ask their respective support team to do that (Possibly by phone). With that information, I believe the easiest…

Hello @eford Thank you for your answer. That's a really weird problem. I was not able to find any possible bugs or incoherencies that you might be causing this issue. I have created an internal support ticket for you so we can better troubleshoot this issue:…

You are welcome, @jdavidge @Félix Réginent can you check if the steps above worked for you?

Hello @lara.wasowski Thank you for reaching out. The comment visibility setting in the work description is the same used for the comments in the issue view and, unfortunately, it'ss not possible to set a default value for that setting at this moment. That being said, we completely understand that this functionality would…

Hello @Ali Adib Thank you for reaching out. Unfortunately, it's not possible to change the fields/columns displayed with the sub-task issues of a parent view or the issues of an Epic view with the new issue view of JIRA, however, we understand how useful this functionality would be, so we created two feature requests to…

Hello @Catherine Tarrant Thank you for reaching out. Per your description, I clearly understand that the "create inline issue" option on the active Sprints is creating issues in your backlog, although the Sprint is selected in the creation. Analyzing other similar cases, I recommend you to check the following steps: 1 -…

Hello Lindsay, Thank you for reaching out. I understand that your current team workflow is to assign the issue to the responsible team lead when escalating it to Tier 2, so you want to track the time taken for the team lead to move it to the correct analyst in Tier 2. Is that correct? Indeed, the best way to track the time…

Hello Xie, Welcome to Atlassian Community. Sorry to hear you are facing this error. Since the error you are facing is a default message for a number of possible problems, can you please provide what is the action that triggered the error message? Did it appear just when you clicked to start JIRA or did it happened after…

Hello Ira, Welcome to Atlassian Community! I understand that you are linking tasks under Stories, configuring the tasks as "Sub-Stories" to split parts of the story work. Have I understood that correctly? Unfortunately, no matter the kind of link you are using between the Stories and tasks, it is not possible to sum-up…

Hello @eford Sorry to hear you are facing this problem. Checking the screenshots you provided, your SLAs and issues are properly configured to display in the SLA report, so I believe your SLA Success Rate Report must be configured with some JQL filter that might be excluding the issues from the chart. Please, follow the…

Hello Aisha, You are welcome! The second option is provided by the Automation for JIRA app, which is a paid add-on you can install in your Server instance by clicking in that link. Once you install it, the menu to configure the rules would be under project settings > Project Automation. Please, let me know if you still…

Hello Saumya, Thank you for your answer. Allow me to go further into the information you provided so we can be on the same page: About this statement: the timezone is different for clients and the reporters are the same. Hence, the use case becomes that one client is in US(New York) and other in Europe, while the reporter…

Hello @Saumya Jain Thank you for reaching out. I understand that you would like to allow your customers to inform the due date of the related ticket together with its related timezone. Is it correct? Could you please elaborate a little bit more on why the mentioning of the timezone in a custom field would not be an option…

Olá Rodrigo, Seja bem-vindo a comunidade Atlassian! Pela sua descrição, entendo que você gostaria de somar as horas registradas de todas as estórias e sub-tarefas relativas ao respectivo épico e adicioná-las no mesmo, para que o gráfico de um específico relatório do Gantt retorne o valor total. Entendi corretamente?…

Hello @HolmanG Thank you for reaching out. You can add existing issues to Epics in the new issue view of JIRA Cloud by performing the steps below: 1 - On your board, click in the issue you want to add in the Epic > Find the field Epic Link and type the name of the Epic: Additionally, you can use the bulk operation…

Hello @MiskaT Sorry to hear you are facing this problem. Checking other similar tickets describing the same error, I believe you are being impacted by a database inconsistency between your custom fields and their respective screens, however, I was not able to find any relation between the error in the custom field page and…

Hello @[deleted] Sorry to hear you are facing this problem. Checking your E-mail handler settings, It seems to be properly configured to skip the previous notification content from the comment added (Strip Quotes = True). That being said, please follow the steps below so we can better troubleshoot the issue: 1 - Is this…

Hello Andy, Thank you for reaching out. Per your description, I believe you have created a custom issue type called "Feature" and added the default issue type Story to your next-gen project, however, you are not being able to display the features and Stories you created in your Kanban board. Is it correct? Please, follow…

Hello @[deleted] Thank you for reaching out. Per your description, I understand that you have stopped using the Tempo timesheets and would like to remove the account custom field provided by the plugin from your JIRA instance. Is it correct? Unfortunately, this is not possible at this moment, so we have created a feature…

Hello Aisha, Thank you for reaching out. There are two options you can choose to send notifications when a specific issue type is linked to an Epic: 1 - Create a filter Subscription - Navigate to JIRA Settings > Issues > Custom fields > Create a select list called "Added to epic", with a single option: "Yes" - Add the…

Hello Salvador, Thank you for reaching out! Per your description, I understand that you need to make sure your sub-task issues creation and resolution dates are equal or between the creation and resolution dates of its respective parent. Is that correct? Please, allow me to bring you some concepts so we can better know we…

Hello Henrik, Thank you for reaching out. I understand that you are looking for a way to automatically add a link to the static Sharepoint document when creating an issue in JIRA, depending on the issue type selected. Is that correct? If you need to link always the same documents for the issue types, you can add their URLs…

Hello Joanna, Thank you for reaching out. In fact, there are some custom fields that might be updated with their default values if not specified in the CSV. In order to make sure your issues did not get with a missing value when performing the update, I recommend the following: - Navigate to your issue navigator > Create a…

Hello Konstantina, Welcome to Atlassian Community! Unfortunately, field-level permissions to hide specific fields depending on the user role/group are not available for none of the JIRA Cloud templates, classic or next-gen. The decision to don't implement this kind of permission is based on several required changes that…

Hello Sekhar, Thank you for reaching out. I understand that you have an issue that was lastly updated on 21st Oct, 2019, however, the updated field is telling that the issue was updated on 31st Oct, 2019. Is it correct? By default, all the update activities performed on JIRA issues are registered under the history tab, at…

Hello Clive, Thank you for reaching out. Unfortunately, JIRA does not have a dashboard gadget that sums the values of specific fields, like time spent or original estimate upon a release. It would be necessary to display the sum of those values to display the three reports you are looking for. Since we understand this…