Petter Gonçalves Atlassian Team

Hello @Paul Wiggers Thank you for reaching out. I was able to reproduce your issue on my personal test site, so I reported the following bug to properly fix this glitch on Jira Service Management: Property jira.permission.comment.denied does not block comments sent by the customer Feel free to vote and watch the bug to…

Hello @Suhas Shastry The JSM version that supports OAuth 2.0 for incoming emails is 4.10, which is the one compatible with Jira 8.10 as you can see in the documentation below: Upgrade matrix Additionally, you can automatically upgrade your JSM to a compatible version with your current Jira environment by following the…

Hello @Aswathi D Thank you for reaching out. By default, the Sprint report provides you with the information on how many issues were included in a Sprint and how many were completed: You can access the Sprint report with the issue count metric by following the steps below: * Navigate to your Scrum board * Click on the…

Hello @Suhas Shastry Thank you for reaching out. The OAuth 2.0 authentication for incoming email servers was implemented on Jira Server instances in version 8.10 that use HTTPS or TSL. You can check in the documentation below all the steps to properly set OAuth 2.0 authentication for your Jira incoming email servers and…

Hello @Aswathi D Thank you for reaching out. You can create a board and use the Epic panel feature to properly display the Epics you want with a progress bar displaying how many issues are completed in each of the Epics. These would be the steps: * Create a scrum board containing all the projects you want to return Epics…

Hello @Diane Reid Thank you for reaching out. By default, the Sprint field sorts the Sprints by creation date (Ascendent order), and I must confess that I never saw the behavior you are facing where the Sprint "The Seven 14.6" would be displayed before "The Seven 12.X". Can you confirm that the Sprint you are looking for…

Hello @Gopi_K Thank you for reaching out. I'm afraid Jira Server does not have a validator that would prevent time tracking fields from receiving a determined value. I believe the best option would be to use Jira automation to properly add a comment in the issue informing that an invalid value was added to the field.…

Hello @James Hadfield Sorry to hear you are having a bad experience with support. I'm a support engineer at Atlassian and will do my best to help you resolve this issue. Checking the tickets you opened with the Atlassian support team, I can confirm my colleague Nathan called you a few hours ago to understand what happened…

Hello @uDMS uDMS Thank you for reaching out. Per your description, I understand that your customers can not log in to their accounts that are being automatically created when they create a new ticket. is that correct? Can you please provide us with the error returned to them when trying to log in? Thanks!

Hello @Sowmya Nallasamy Thank you for reaching out. I saw you already created an internal ticket for our support team. Please, feel free to share the root cause of the problem and resolution steps once your interaction with Atlassian support is finished. Thanks!

Hello @Saša Thank you for reaching out. Please, note that the documentation you are following is related to Jira Server application, so its steps do not apply to your Jira Cloud environment. You can follow the documentation below in order to properly enable and configure OAuth 2.0 authentication for Jira Cloud apps: OAuth…

Hello @Pascal Grunau Thank you for reaching out. Unfortunately, it is not possible to prevent the creation of Atlassian Accounts for a specific claimed domain. We have a feature request created to consider this possibility in the future: Ability to restrict Atlassian account creation for claimed domain Please, feel free to…

Hello @Anthony Morais Thank you for reaching out. As your issue is not reproducing when using incognito mode, the root cause of the issue seems to be related to some configuration or extension in your browser. Please, try the steps below to properly troubleshoot your issue: * Update your browser to its latest version * Try…

Hello @Kristine Gemici Thank you for reaching out. Unfortunately, It is not possible today to set a default view for all new plans created on Advanced Roadmaps. At this moment, saved views can only be used in the plan it was created for. We have a feature request to consider the implementation of saved views to any new…

Hello @Lorraine Jones Thank you for your detailed message. The error you are facing happens when the Due date field is not set correctly with a valid value. That being said, I'm afraid you (or your team) may have created a custom field called Due date, so when you fill this field in the issue view it does not properly…

Hello @Patrick Iverson I've properly opened an internal ticket to help you with this thread, as we will require some information from your Atlassian organization. Let's continue your support on the internal ticket. Thanks! 

Hello @jared Thank you for reaching out. You can use an automation rule to properly check the resolved issue against a JQL query, properly checking if the issue matches specific keywords on any text fields and adding the relevant labels. These would be the steps: * Navigate to your project > Project settings > Automation *…

Hello @Lorraine Jones Thank you for reaching out. Please, let me summarize your scenario to confirm we are on the same page: Per your description, I believe you're talking about the basic roadmap feature provided by the standard plan of Jira Cloud and not the Advanced roadmaps provided by Jira premium. Additionally, I…

Hello @Chalani De Silva Thank you for reaching out. Indeed, it is not possible anymore to create new components from the create issue screen in the new create issue experience. We created the following bug to fix this limitation: It's Not Possible to Create a Component from the Create Issue Screen Feel free to vote and…

Hello @Aga Bailey Thank you for reaching out. The best option to display the percentage of resolved tickets by each assignee/member would be the dashboard gadgets Issue statistics or Two dimensional filter statistics, however, the first option only has a single dimension (Assignee or status), while the second one displays…

Hello @Bruno Frade Thank you for reaching out. Per your description, I understand that you would like to prevent external people (not linked to an Atlassian account) from sign-up to your project portal, however, you still want your team (Which currently has an Atlassian account) to be able to self sign-up on the project…

Hey @Emilie Corcoran Regarding the branch "For linked issues", you can find this by following the steps below: * Go to your automation rule > Click to edit * After adding the rule trigger, click to add a new branch > Branch rule/related issues * Select "Linked issues" Also, to include cross-projects in your automation, you…

Hey @Ronnie Wan Per your description, I understand that when you add a field to the "Request form", it gets removed from the tabs you created in the internal issue view. Is that correct? There is a public bug created to properly change this behavior: Fields in the tabs get moved to the General tab Regarding the displaying…

Hey @Mit Tolia Thank you for bringing this up. I have good news regarding the backup automation export for Jira and Confluence: Atlassian is currently developing the feature to automate backups for both Jira and Confluence directly from the UI, although this functionality might take some time to get deployed. You can check…

Hello @starrr, Thank you for reaching out. Indeed, the message received from the CSV import client when a specific field value is required from a validator or a field configuration is too vague. We created the following feature request to improve this message when importing issues from a CSV file: Improve error message for…

Olá @Alerta - SOC - IT4US Obrigado por entrar em contato com a nossa comunidade. Você pode selecionar se deseja enviar notificações para toda a organização do relator (ou não) editando os remetentes das notificações de clientes do seu projeto JSM. Estes são os passos: * Navegue até seu projeto > Configurações do projeto >…

Hello @Malka Jackson [Isos Technology] Thank you for reaching out. Please, notice that the documentation you're referring to is related to JSM Server and Data Center, and not Cloud: Unfortunately, the option to vote from the customer portal is not available for JSM Cloud yet. There is a feature request to consider the…

Hello Nidhi@123 Thank you for reaching out. About the first behavior you mentioned, I totally agree with you that a 200 response is not what is expected when adding a wrong username in the authentication of the REST Call. We create the following bug to get this properly fixed: Misleading response when running the Rest API…

Hello @Daud Rauf Thank you for reaching out. Currently, I believe there's no API endpoint to return only active or inactive users on Atlassian applications. We have a feature request created to consider this possibility in the future: Provide an API to search/exclude from search inactive users Feel free to vote and watch…

Hello @Jira Customer Thank you for reaching out. Per your description, I understand that the portal customers in your JSM site also have accounts on your Active directory, so you would like to sync them from the AD directly. Is that correct? If I properly understood your request, you might have different answers depending…