Petter Gonçalves Atlassian Team

You are welcome, Blair! Have a nice day!

Hello Peter, Indeed, you will need to configure your sub-task workflow to allow transitions between any status to make it work since the parent issues can be in any status. If you need further help customizing your workflow, please let me know.

You are welcome, Rebecca! Have a nice day!

Hello Shankar, By default, attachments are moved together with the issues when using bulk operation to move them from one project to another, as commented by @Josh loe. To perform it, you can check the instructions provided by Tuncay in the answer below: - How to bulk move issues to another project Additionally, to keep…

Hello Blair, The smart values you used on your Automation rule has properly worked for me - It properly added the Epic and Story summaries to the sub-task. Here's the rule I executed: That being said, I believe that something might be blocking your Automation rule. Please, check the Audit Log of your automation and check…

Hello Maciej, I believe the fields affected by this problem are Radio button custom fields, is that correct? Indeed, we have identified this bug with Radio button and properly reported it to our development team: - Radio button custom field disappears on clicking in new issue view Please, add yourself as a watcher to be…

Hello Torsten, Welcome to Atlassian Community! The Detail View displayed in the first screenshot you sent is related to the New Issue View and each user can turn it on/off as they want. To deactivate it, the user can perform the following steps: - Click on the profile picture at the left-down corner > Personal Settings -…

Hello Peter, This functionality can be easily achieved using Automation for JIRA. You just need to configure the following rule: Please, let me know if it works for you.

Hello Chris, Can you let us know what is the type of your custom field? Basically, you can clear the value of custom fields by configuring the post function Update Issue Custom field in the workflow transition. Here are the steps: 1 - Navigate to your Project > Project Settings > Workflows > Click to Edit your workflow…

Hello Shaheedah, Welcome to Atlassian Community. To use a Service Desk portal, you must sign-up for the JIRA Service Desk Application (Cloud or Server). For more information, check the documentation below: - JIRA Service Desk Application To keep the Service Desk portal available only for your internal users, you just need…

Hello Pia, Welcome to Atlassian Community! The best way to achieve your need is by adding a specific character/word in the default response to remove it from the search. Of course, this character/word should not be used in other comments that are not with the default response. Explaining better, let's suppose your default…

You are welcome, Justin! I'm glad to know we were able to help you!

Hello Andrew, Welcome to Atlassian Community! Checking the releases page of my project, it indeed always filter for the unreleased version in a first view, however, you can easily click in the drop-down and select the released versions to be displayed: I understand that you needed this view to be appearing when you first…

Hello Jesse, Welcome to Atlassian Community! You are correct. Your requirement can be achieved using Security levels. Please, let me better explain how it would work: An Issue security level is basically a custom field that restricts the access to an issue only to the users/groups that are properly configured to it in the…

You are welcome, Jeroen. Have a nice day.

You are welcome, Eduard. Have a nice day.

Hello Nicolas, I would look for the following possibilities: 1 - Confirm that the user is added to JIRA Core Application access 2 - Check if there are any security levels added to the issues which are not configured for the user 3 - Run the integrity checker application checking for duplicate permissions. P.S: Preferably,…

Hello Jeroen, Welcome to Atlassian Community! Indeed, the new issue view of JIRA is still a lab experience so our developers are still working to implement some key feature to it, including the worklog tab. That been said, you can check their progress in the implementation of this feature in the link below: - As an user,…

Hello Unnati, Unfortunately, it is not possible to clear votes of a JIRA issue on the Cloud platform. There is a feature request opened to implement this functionality: Manage (at least clear) voters of a ticket as project administrator Also, feel free to watch and vote on the feature request to increase its priority and…

Hello Eduard, Unfortunately, it's not possible to add only tables or pieces of a Confluence Space to a JIRA issue, however, you can link an entire Confluence to a specific ticket. You can check how you can do that in the documentation below: Integrating JIRA and Confluence Additionally, if this functionality is not enough…

Hello Jennifer, The Auto-Complete feature can be achieved by using some JavaScript syntax on your issues fields. For a Multi-Select Custom field, you can check the explanation of Benji below: - Adding Auto-Complete to a Select list Basically, these would be the steps: 1) Create a custom field that uses a multi-select list…

Hello Ben, Welcome to Atlassian community. I can help you with two possible ways to perform this calculation: 1 - Export your issues to CSV (Excel) and use the application to calculate the Mean time to resolution externally 2 - Use Script Runner plugin to create a new custom field and calculate the difference between the…

Hello Nidhi, thank you for raising this question. Can you please give us more details of what would be the requirements of a Purchase Order? I mean, what kind of fields, features and workflow this should have? Basically, you can create a new issue type called Purchase Order to properly register/track the progress of it. To…

Hello Chris, Welcome to Atlassian Community! Could please let us know what you mean when you say "I can only execute tests"? Are you meaning the initial transition to TEST-EXECUTED that you configured in your workflow? More specifically, can you please tell us what is the workflow transition that you are not being able to…

Hello Justin, Welcome to Atlassian community! Unfortunately, the functionality you are looking for cannot be achieving using only JIRA application, however, it can be easily implemented if you use a plugin. My recommendation would be: 1 - Install the Plugin Automation Lite for JIRA Cloud - 300 free executions per month 2 -…

Hello Vinay, Welcome to Atlassian community. Indeed, we understand that these options could be very useful to better specify your Time Tracking Reports and we have already requested this functionality with our development team. The most complete solution that we have requested so far would be to use JQL filtering in the…

Hello Rebecca, Indeed, that's the reason why it is configuring your issues with 3 days in the time tracking field during the import. To configure your instance to properly handle the information as you need, you must perform one of the two steps below: 1 - Configure 28800 seconds in your import file (The equivalent to an…

Hello Carlota, Indeed, there's no way to add extra colors to Epics on JIRA for now, however, a feature request was already opened for this matter with our development team. To be aware of the progress of it, check the feature request below: - Ability to add More Epic Colors in JIRA Cloud Also, feel free to vote for it to…

Hello Maciej, Welcome to Atlassian Community! I can confirm to you there is no kind of restrictions that would block non-admin users to see the default JIRA fields in the Issue details view. That been said, I believe your view is someway different from the users you are mentioning or the fields are related to plugins,…

Hello Paul, Thank you for reaching our Atlassian community! I understand that you would like to build a query to return all epics associated with project A and children associated with project A's epics without needing to specify the issue key of the Epics, but perform a sub-query to select the Epics by projects or any…