Petter Gonçalves Atlassian Team

Hello María, As you may know, the new issue view of JIRA is still on Beta, so our developers are still implementing new functionalities to it. That being said, the ability to Edit/Delete worklogs on JIRA Issues has already being requested and our developers are already working on it: - As a user, I'd like to edit a work…

Hello Rafael, You will need to use an add-on to configure this functionality and there are several that you can use to configure it. That being said, my recommendation is to use Automation for JIRA (300 free executions per month) and configure a rule like the one below:

Hello Mick, You can configure a JSON Script using JIRA REST API to delete a custom field option when you need with the following call: DELETE /rest/api/3/field/{fieldKey}/option/{optionId} Please, check the documentation below to get more details about it: - Delete Issue Field Option

Hello Michael, Checking other customer reports about this error, I could found out that it is usually related to a failure when uploading attachments to JIRA issues, but I could not find anything related to Slowness because of this error. This failure can be caused by several reasons as connectivity problems or even…

Hello Venkateswara, Unfortunately, that’s not possible to achieve out of the box. However, you can configure your own hook to implement this kind of restriction when performing the commit. I recommend you to look for help on our Development Resources to check how you could configure it.

Hello @John Schuster. each user can turn-off the new issue view by clicking on the profile picture > Your profile and settings > Personal settings and toggle the switch for the New Jira issue view. For more information about it, check the link below: The New JIRA Issue View

Hello Jon, You can use the following rule to copy your sub-task fields to the parent: P.S: Note that I used the summary field as an example.

Hello Marcela, As you can check in the documentation below, the Administrators Global permission is required to perform any actions (Create, edit, access) regarding Issue collectors: - Using the issue collector

Hello Itamar, Unfortunately, it's not possible to get this information using the own JQL queries of JIRA. The only way I was able to find this information is by using the plugin Time Reports for JIRA, where you can check the time in status for each issue: P.S: Note that the Time in Status report accumulate if an issue is…

Hello Pedro, The plugin is working just fine for me. What is appearing empty? The filter is not displaying any issues at all or the issues are properly displaying but the column with the statuses are not displaying any values? If possible, send us a screenshot so we can properly understand what is happening.

Hello Dina, Can you please tell us where are you facing difficulties to use the plugin? The way you configure it is very intuitive, however, for some functionalities, it can be challenging. Can you please tell us what are you trying to achieve?

Hello Akhil, There are several plugins that provide the same functionalities as JSU. The most similar one I believe is JIRA Misc Workflow Extensions. You can also try Automation for JIRA. This one is not based on post functions, however, it can provide the same functionalities using Automation rules.

Hello Vivek, After some time digging about this feature, I find out that this functionality is not possible at this moment. We had a feature request in the past asking for this functionality, however, our developers have decided to not implement it due to the small number of requests:…

Hello Vichith, To edit/add the priority options on your JIRA site, you can navigate to JIRA Settings > Issues > Priorities. Please, let me know if the new options appears to you when creating the issue from e-mail.

Hello Sebastian, There are several plugins that you can use to achieve this feature. I can think about four possible options: 1 - First, I would recommend Scripting Suite for JIRA as a free solution so you can build a script like the one informed in the link below:…

Hello Adrian, Yes, it is possible to move all your issues from a Core project to a Software project. You can even configure the same workflows if you want to keep the same statuses on the issues or change it to a different one. To do it, you can configure a filter to return the issues of your Core project and use the Bulk…

Hello Sai, Sorry, I have misread your question. I thought you were meaning Import when actually you were talking about the export feature. The query you are exporting will return all the issues created, however, it will not export the Screenshots or any kind of attachments of your issues. The Attachments can be exported…

Hello Chethan, I saw you marked this issue as resolved. Can you please let us know how you managed to work around the last problem you were having?

You are welcome, Alison. Thank you for sharing the problem resolution.

Hello William, I think that maybe you have misunderstood how the request type feature works. Request Types are required to create issues through the Customer Portal, while you can create issues without a request type internally on JIRA. In order to allow a request type to be selected for a specific issue type once it's…

Hello Brad, To create a filter to search for sub-tasks where the parent issue meets certain criteria (issuetype = Fulfillment) you will need to use ScriptRunner plugin to configure the following query: issueFunction in subtasksOf("project = XXX AND issuetype = Fulfillment")

Hello Jon, Unfortunately, I think it's not possible to create multiple sub-tasks based on a Custom field number using Automation for JIRA. I think the only possible way to do it using Automation for JIRA is by configuring a single action for each sub-task created. Also, if you are familiar to Groovy Script, you can use the…

Hello Sai, To import attachments using CSV format, you must specify the URL of your attachment in an Attachments column within your CSV file. For example: Assignee, Summary, Description, Attachment, CommentAdmin, "Issue demonstrating the CSV attachment import", "Please check the attached image below.",…

Hello Rupa, The Status field is not a custom field, so I believe that maybe your JIRA is not localizing to correct status field when mapping it. Can you please let us know what is the steps you are taking to the import system? The correct steps are: JIRA Settings > System > External System Import Can you also provide us…

Hello Pedro, You will have to use a plugin to have the information you are looking for. My recommendation is the Time Reports for JIRA Cloud which provide you a simple report that displays the time status for the issues you want:

Thank you for sharing it, Olivier! Have a nice day.

Hello Rupa, Can you confirm if you have properly mapped the status field when doing the import? The only possible reason that can cause this behavior is when the status is not properly mapped in the Import client: Even if the values you have added to the CSV status field does not exist in the Service Desk workflow, it will…

You are welcome, Rick. Have a great day!

Hello @Rick Chabot, Please, refer that the workaround provided before was for the Server Platform and not Cloud. For the Cloud platform, you're correct to say that we don't have a way to update the completion date since we don't have database access in Cloud. In fact, the completionDate of the sprints are not editable even…

Hello Simon, The idea of the Agility project is to provide customers with an easy, simple and straightforward way to configure their business. That being said, the release feature is not available on Agility at this moment since it would add more complexity and avoid the initial idea of a simple template. If you think this…