Petter Gonçalves Atlassian Team

Hello Dhiraj, There are only two features that can be blocking you to see that specific issue: - The issue is from another project and you don't have the proper Permissions to see it - You are being blocked by an Issue Security Level If you are not a site-Admin, I would recommend you to contact him to check both options…

Hello Vishal, Can please confirm what is a TT? Per your description, it seems you have some kind of automation that is creating a ticket everytime you open and close another ticket. Is that correct?

Hello Scott, I understand that you are looking for a view to display all the fields mentioned in your description (component, start date/time, end time, duration, and planned/unplanned) in your Service Desk. If I understand it correctly, all the fields above already exists on JIRA, excepting duration and planned/unplanned.…

Hello Carol, Can you please provide us screenshots displaying where you are able to set new watchers using the old view and where you would expect to set the field in the new view? The New JIRA view has been updated recently, so I would like to have more context to know how it is currently displaying in your JIRA Version.

Hello JD, In JIRA Cloud you can only create the hierarchy Epic-Story-Subtask, however, you can add multiple hierarchy levels using Portfolio for JIRA. Please, start a free trial of this plugin and check if it gives you the functionality you are looking for: - Portfolio for JIRA For more information about it, check the…

Hello Carol, You must have both permissions below on your project to be able to see and manage other watchers in the issues: View Voters and Watchers Manage Watchers To properly check/add these permissions to your users, you can navigate to Project Settings > Permissions

Hello Legna, You must be in the group to be able to share a dashboard. Can you please check if you are added to the group you are trying to share the dashboard with?

Hello Celso, I'm sad to hear that JIRA works in a different way you expect. We are always working to give our customers a better experience, so feel free to give your feedback to our developers on https://jira.atlassian.com for anything you think that could work in a more efficient way. Additionally, I would like to tell…

Hello Renzo, you can check the documentation below to use the Average time in status Gadget: https://community.atlassian.com/t5/Jira-questions/How-do-I-get-the-quot-Average-Time-In-Status-quot-chart-to-work/qaq-p/227721 Also, there is a plugin that provides this functionality in more formats: - Time Reports

Have a nice day you too, Lito. Please, feel free to accept my answer to help other Atlassian customers in the community.

Hello Lito, In the same page, Click on Advanced search and the option will be displayed in the same Icon.

Hello Burkhard, The behavior you mentioned is intended by the application since the Service Desk Support e-mail should only be used to receive Support requests on JIRA, that's why this e-mail doesn't even have an accessible mailbox. In fact, it was not working like this a while ago and the behavior was reported and fixed…

Hello Lito, Thank you for the clarification. Yes, you can import any data to specific issue fields that you want. Looking at your screenshot, it seems that you have configured a new Custom field to receive the Checklist topics. That being said, you can export one of the issues that you have manually populated the custom…

That's a really strange behavior, Matt. The only possible root cause that I can think without further investigating the issue is that maybe someone has configured a custom field and named it as Resolution instead of using the correct system field. Can you check if you more than a single Resolution field?

You're correct, Matt. I believe that for some reason, the system is not recognizing your imported issues with a valid resolution, so a manual update on resolution must probably set the correct resolution. I also would like to clarify a few things: - Is the problem happening for all issues in your system? Or only for the…

Hello Matt, In that case, I recommend you to try the workaround suggested before and check if it fixes the issue. If the problem keeps happening, please open a ticket with our support team so they can further investigate it: https://support.atlassian.com/contact/

Awesome, Nageswara. Please, feel free to accept my answer so it can help other customers in the community too.

Hello Nageswara, The following call should work to edit a custom field: PUT /rest/api/2/issue/{issueIdOrKey} For more information, check the documentation below: Edit Issues REST API

Hello Philip, You can use JIRA Automation lite plugin to configure a rule that will change the assignee of issues based on a JQL filter. Check the example below: Here are the plugins: JIRA Server: Automation Lite for JIRA JIRA Cloud: Automation Lite for JIRA Cloud

Hello Celso, As mentioned by Matthias on this Question, you can perform a search with a JQL to select the issues you need. Have a look at the API Documentation to search and try with a JQL like the one below, where 2.2.2 is the number of the version you're interested in: fixVersion = "2.2.2"

Hello Adam, You can achieve this functionality using one of the options below: 1) Use the add-on Automation Lite for JIRA: This is the most simple and efficient option to achieve your need. You just need to configure the Automation Rule just like I did in my test instance for your project, Scheduling the rule to be…

you are correct, Elif. Sorry that I have missed this detail on your description. The sub-task Sprint cannot be changed since they will always be on the same Sprint as their Parents. This is intended by the Scrum method.

Hello Elif, You must have the following permissions on your Permission Scheme to move an issue to another Sprint: - Manage sprints - Schedule issues Can you confirm with the Permission Helper that you have both permissions added to your user? You can be also facing an integrity problem with your permissions, so I recommend…

Hello Pallavi, There is no limit to bulk creates issues using Rest API on JIRA. The issues will be created sequentially not matter the number, however, the call can be throttled due to the server being unresponsive for high CPU or high memory usage, depending on the number of issues and capacity of your server.

Hello Lito, What kind of checklist are you trying to import? you can import checklist items as issues or even import your whole checklist into a single issue, however, we would need more details to know what would be your goal. We will be waiting for your answer.

Hello Aaron, Unfortunately, there's a limitation on the filter that can be applied on Slack Integration. It can be configured by issue types and priority, as you mentioned. There is a feature request created to implement a JQL Filter to specify JIRA notifications sent to Slack channels, just like it was configured for…

Hello Matt, I believe that you're facing an index problem here. Have you already tried to re-index your JIRA after the import? Also, I believe that maybe the integrity checker would fix any possible errors in the database parameters. Please, try both procedures (Not at the same time) and check if it corrects the problem.…

Hello Matt, I believe that you're facing an index problem here. Have you already tried to re-index your JIRA after the import? Also, I believe that maybe the integrity checker would fix any possible errors in the database parameters. Please, try both procedures (Not at the same time) and check if it corrects the problem.…

Hello Pascal, In order to change the Request Type of a Service Desk issue, it should be mapped to the related Issue Type of the issue. To check what Request types are mapped to each issue type you can navigate to your Project > Project Settings > Request Types. If the request type you are trying to change your issue to…

Hello Matt, Can you check if you have properly added a valid Resolution for the Tasks you imported? Most of the reports on JIRA only consider an issue resolved when the Resolution is properly configured, not mattering the Status of the issue. If that's the case, you can follow the workaround mentioned in the documentation…