Petter Gonçalves Atlassian Team

Hello @[deleted] Thank you for reaching out. Per your description, I understand you would like to add the summary and key of the new issue created in the automation above to the previous existing issue from where you triggered the automation. Is that correct? You can use another automation rule to achieve that, you just…

Hello @Benoit Thank you for reaching out. Per your tags, I see you are using the Jira Server application, not Cloud. Is that correct? If you are using Jira Server, I'm afraid there is no functionality that you can use to copy values from a parent issue to a sub-task. We have the following feature request to implement this…

Hello @Shane We can absolutely provide you more context and information on how you can achieve your goal with the Advanced roadmaps. In order to provide you with more specific information, we suggest you open an internal support ticket with us at the portal below: https://support.atlassian.com/contact/#/ In that internal…

Hello @Shannon Griffin I'm glad to know you were able to import your issues as sub-tasks. Since the community is a public portal, I suggest opening other questions about each of the other behaviors you are facing that are not working as you expect, so we can better organize it and the answers could be easily found by other…

Hello @Erika Shek You can easily copy whole text fields using Smart values, however, I'm afraid it is not possible to copy only specific lines from a text field using automation for Jira. The best way to achieve it would be to use multiple fields to detail the information you need and copy it to your description field…

Hello @Saurabh Soni Can you confirm if you were using Jira Server or Cloud? The problem you were facing seems to be caused by a failing re-index, which is usually caused in the server application. @Jovita Mathias is using a cloud environment, so the re-index happens automatically after the change of estimation. Please,…

Hello @Yasir Ali Welcome to the Atlassian Community! In order to have more details about what could be causing the error you are facing, we need you to provide us with the error returned in your atlassian-jira.log in your installation directory when trying to create the project. You can check the documentation below to…

Hello @Gianmarco Reverberi Welcome to the Atlassian Community! Please, follow the steps below to properly troubleshoot the issue: * Try to use a different browser to open your issue in incognito mode, confirming if the field is not being translated by any browser settings or extensions. * Check if you are not using any…

Hello @Blake Falanga Thank you for reaching out. Per your description, I understand you would like to copy some specific fields from their related Epics when you create them. Is that correct? You can use an automation rule to properly do it. These would be the steps: * Navigate to your Project > Project Settings >…

Hello @Garrett McCreery Thank you for reaching out. We completely understand the goal to use Project roles instead of groups in the manual trigger of Automation rules. In fact, It is not possible to use project roles today because the manual trigger functionality was initially configured to work in both Projects and Global…

Hello @Harry Bob Thank you for reaching out. Considering the context you provided, this would be how the rules above will work: It will not matter if you mark the "Only include issues that have changed since the last time this rule executed" option. Since the rule action (comment) will always update the issues in the JQL,…

Hello @Jawed Ali Thank you for reaching out. As you can see in the official documentation of CSV import, Time Tracking fields (Time Spent, Original Estimate, Remaining Estimate) can only be imported in seconds using the CSV import functionality. The only exception would be if you set your time tracking to be estimated in…

Hello @Stephan Nowak Thank you for reaching out. Per your description, I believe you might be facing the bug reported below: When exporting issues to CSV ( Current fields), for saved filters. If we have chosen certain columns in the “Filters” section, its ignored and columns from ‘Default’ section gets exported Explaining…

Hello Shane, Indeed, the Advanced roadmaps allow you to add multiple issue types to the same hierarchy (Including Epic Hierarchy). Let us know if you have any other questions.

Hello @mtruelove The specific add-on you mentioned (JQL Booster Pack) is only available for Jira Server, however, you got some other options as explained before. Let us know if you have any other questions.

Hello @Shannon Griffin Indeed, the bugs I mentioned about Next-gen projects cause the sub-tasks to not be mapped as an issue type in the CSV import, so it is not possible to import sub-tasks to Next-gen projects. Sorry if I wasn't clear about this. Just like I mentioned before, a possible workaround if you want to use a…

Hello @guido spiritoso Sorry to hear you are facing some problems with Jira Application. Once you verified your domain, you can follow the steps below to properly edit the e-mail of a managed account: * Navigate to admin.atlassian.com, and log in with your organization admin account * Select Directory > Managed accounts *…

Hello @James Dean Sorry to see you are facing problems to add some customers to your service desk project. In order to properly troubleshoot it, please check the information below: * Add the users that you are not being able to add on a separate list. Then, check under User management > Users if the user is not created but…

Hello @mtruelove Welcome to the Atlassian Community. Per your description, I understand you are trying to return child issues based in the values added to the parent fields. Is that correct? Unfortunately, the JQL search of Jira application does not have a function to search based on parent fields, however, we understand…

Hello @Bryan Faxel Welcome to the Atlassian Community! Non-admin users can import issues to a CSV file using the import client on the issue navigator page. These would be the steps: * Click on filters drop-down at the header of Jira UI > Advanced Issue Search * Click on ... > Import Issues from CSV: P.S: The client…

Hello @Max Benek Thank you for reaching out. Indeed, Jira does not have a comparison type to calculate the number of days or hours added to a field. We have a feature request to allow that kind of comparison in workflow conditions: As an admin, I'd like to set a date comparison condition in the workflow as a JQL search…

Hello @mike potashnick Thank you for reaching out. You can use the Time tracking field to record the estimated time to complete an issue in hours and days, as you can see in the documentation below: Configuring time tracking Basically, this field display three pieces of information in your issue view: Original Time…

Hello @Ali El Banna Thanks for reaching out. I noticed you created an internal support ticket about this problem, describing that you were able to solve your issue by selecting the correct language. Please, let us know if there is anything else we can help with.

Hello @JiraSine95 Thank you for reaching out. Can you please confirm what is the version of your Jira Service desk Server? In Jira Cloud application it is possible to create a new issue when a comment is added to a closed issue, just like the latest version of Jira Service desk Server: Together with your Jira SD Version,…

You are welcome @Janene Pappas Have a nice day and let us know if you face any other questions.

Olá @Henrique Degan Fico feliz de tê-lo ajudado. Qualquer outra dúvida, fico a disposição.

Hello @Krasimir Matev Thank you for reaching out. The field that must be filled with your user when you sign-up to work in a new issue is the assignee field. once you do it, it's easy to create a filter to return the list of issues you have assigned in the day. These would be the steps: * Click in the Filters drop-down at…

Hello @support for vo Thank you for reaching out. I believe you might be misunderstanding some concepts from Jira Service desk, which is natural due to the complexity of the Application. Please, allow me to provide you with some concepts and details so we can confirm we are on the same page here: About this sentence: •…

Hello @Виктория Thank you for reaching out. Per your description, I understand you are looking for kind of an "SLA field", that will basically count the time spent until a specific action (Issue transition) is completed, considering your business hours. Is that correct? Unfortunately, Jira Software does not provide this…

Hello @Anne Karin Stensland Thank you for reaching out. Per your description, I understand you are trying to configure quick filters in your Next-gen project. Is that correct? Unfortunately, quick filters are not available for Next-gen projects yet, however, we understand how useful this feature would be, so we created the…