Petter Gonçalves Atlassian Team

Hello @Lars Gruber Thank you for reaching out. Indeed, the translation selected is not being applied to locked fields in the Jira issue view. This behavior is a known bug with Jira application, and is reported in our official portal for tracking and fixing: Jira Service Desk locked fields are not translated in the new…

Hello @Marius Fischer Thank you for reaching out. Unfortunately, the only fields that can be edited directly from the queue view are the Assignee and Status fields. We currently have a feature request to consider the implementation of this ability for more fields in the queue view: Add Options to Inline Edit Function in…

Hello @Darren Friedrich Thank you for reaching out. Can you confirm if you added an entirely new email address to your project? or have you just edited the email prefix and are still using the default Jira cloud email address? I recommend checking if the outbound email IPs listed in this documentation are properly…

Good catch @Trudy P Claspill :) 

Hello @Fred Thank you for reaching out. Can you please provide us with a screenshot of your automation? Without further investigation, the only thing I think that might be causing your issue is that you have possibly flagged the option to "Only include issues that have changed since the last time this rule executed", so…

Hello @le_admin Thank you for reaching out. Indeed, the behavior you are facing is a known bug with Jira application. We reported it in our official portal for tracking and fixing: Non-English language in-site and app notifications contain strange characters Feel free to vote and watch the bug to increase its priority and…

Hello @Eduardo García Moreno Thank you for reaching out. Per your description, I understand you are facing the following scenario: * You configured a validator requiring the field "Aceptado calidad" to be added with a valid value. * You have three different issue types (Story, Bug, Task), however, you only added the…

Hello @Joyce Anderson Thank you for reaching out. I see your question is flagged as Jira Service Management Cloud, however, the SLA goals report is only available on Jira Service Management Server. Can you please confirm if you are using Jira Server or if you are using a third-party plugin on Cloud to provide that report?…

Hello @Disha Gawande Can you confirm what project type you are using as I asked in step 3 (Company or team-managed)? Also, can you confirm if the workaround provided in step 4 worked for you? Thanks!

Hello @Sam Bartolome The bug seems to affect Jira Server applications older than 2016, so I believe you are probably facing a totally different behavior. In order to further troubleshoot it, could you please create a new support ticket at Atlassian Support? In an internal ticket, we'll be able to dig deeper into the logs…

Hello @Tiago Nogueira Thank you for reaching out. Per your description, I understand that you are not being able to remove custom fields from your task issue type in your project. Is that correct? Please, provide us with the following information to further troubleshoot: * Can you confirm if more details of the error are…

Hey @Juan Carlos Cardenas Padilla Per your description, I understand you need that new issues created to get automatically assigned to specific users if they have a specific component. Is that correct? If I understood it properly, you can simply add a condition to confirm the component field and a new action to add the…

Hello @Balabay Thank you for reaching out. You can schedule an automation rule with a cron expression to properly create an issue and send a notification every 5th day of the months you want. These would be the steps: * Navigate to the project where the issue should be created > Project settings Automation * Click to…

Hello @Disha Gawande Thank you for reaching out. Per your description, I understand that you are not being able to edit field values in your Story issues. Is that correct? Please, provide us with the following information to further troubleshoot: * Can you confirm if more details of the error are provided in the Browser…

Hello @Juan Carlos Cardenas Padilla Thank you for reaching out. The automation you created seems to be correct, so I would check the following steps to find possible blockers: * The automation client act in the same way as any other users in the application. That being said:* Confirm that the same issue type (tipo de…

Hello @Yojhan Thank you for reaching out. Per your description, I understand that you would like to get a statistic for the agents' activities in your JSM site based on a recent time range. Is that correct? I believe that maybe the gadgets "Issue statistics" and "Two dimensional Filter statistics" may provide you with the…

Hello @Joaquín Ernesto Romero Albornoz Thank you for reaching out. Atlassian applications usually do not overflow your browser cache, so it's possible that some extension or script might be causing your cache to be overloaded. I would recommend the following approach the avoid the problem: * Check if any extension/script…

Hello @Mathew Stucki Thank you for reaching out. You can properly get the percentage of tickets moved from QA by identifying those issues with a field and using the Issue statistic gadget on a dashboard. These would be the steps: * First, create a JQL query to identify the issues that were previously in the status "QA" and…

Hello @Richard Rykowski Thank you for reaching out. Per your description, I understand that you are looking for a way to automatically sync your issues between multiple sites, so you would not need to copy comments, details, and any other information from one issue to another. Is that correct? Unfortunately, Jira doesn't…

Hello @Dorothy Callahan Thank you for reaching out. Checking your screenshots, I can confirm your customer is not receiving notifications of that specific issue because the notifications were manually turned off by the customer. The customer turn on the notifications by simply clicking on the "Notifications Off" button…

Hello @Ste404 Thank you for reaching out. I'm not sure if I totally understood your automation logic, but you can use the smart value {{issue.parent.key}} to properly copy the parent key to the labels field of a child/linked issue: Can you confirm if that works for you? You can check the documentation below for more…

Hello @Sam Bartolome Thank you for reaching out. At this moment, there's a bug that causes the Epic link to be cleared when creating a second issue using the issue create screen: Epic link isn't copied when using Create Another to create multiple issues Can you check the bug steps and confirm if that's the bug you are…

Hello @Devant IT Solutions Pvt. Ltd. Thank you for reaching out. Please, follow the steps below In order to further troubleshoot the issue: * Try to clear your browser cache * Check if the same problem happens in a different browser and on incognito mode * If the problem still happens, please access your browser dev tools…

Hello @JADI SRISHYLAM Thank you for reaching out. The queues you have on a JSM project are loaded based on a JQL query. The only reason that can cause issues to don't be displayed on a specific queue is that they are not matching the JQL query configured for that queue. Let me give you an example: The queue of your…

Hello @Dominik Březina Thank you for reaching out. Unfortunately, it is not possible today to set a centralized incoming email address for multiple JSM projects. We have the following feature requests to consider this possibility in future releases: Ability to use the same customised email address on multiple JSM projects…

Hello @Aswathi D Can you provide us with more details about the feature you are looking for? What kind of information/data do you need to be displayed exactly in the bar chart? Thanks!

Hello @James Crook Thank you for reaching out. Unfortunately, the calendar of Jira Work management can not be shared with other calendar applications. We have a feature request created to consider the integration with Google calendar: Integration With Google Calendar Feel free to vote and watch the suggestion to increase…

Hello @Elizabeth Reon Thank you for reaching out. The landing status of the issue will always be the one that the create transition is directed to (Waiting for Support). A possible approach that can match your scenario would be to create an automation rule that will identify when an Approver is added and automatically move…

Hello @Vivek Bansal Thank you for reaching out. Yes, you are able to sign-up for multiple Atlassian organizations with the same email address, which domain is claimed or not. Those organizations will all be centralized for you on the site https://admin.atlassian.net, as you'll be the org-admin of any new organizations you…

Hello @Urmo Thank you for reaching out. Per your description, I understand that you would like a specific field in your personal task to get updated when that same field is updated in any cloned issues. Is that correct? If that's what you are looking for, you don't need any JQL to do this, but only define the correct link…