Petter Gonçalves Atlassian Team

Hello, I just would like to give a quick update that we have the Atlassian Developer Community to properly address development questions: https://community.developer.atlassian.com/ The mentioned portal was specifically created for development questions, where you will find articles and suggestions from third-party partners…

Hey @Rachid Amajoud I know this is an old thread, but were you able to find a solution for your last request? Please, share your solution with the rest of the community or let us know if there is anything else we can help with.

Hello, Just a quick update on this thread: Question 1: Just as mentioned by @Walter Buggenhout, Create and invite users to Jira is basically the same thing, where you can select if you want to send a notification to the user or not. Question 2: Indeed, it is not possible to allow specific users to access issues in Jira…

Hey @jacob delddd I know this is an old thread, but have you come up with any solution? If not, can you please let us know if you are still facing the problem and what is the action that triggers the problem?

Hello, Since this is a development question, I believe the correct place to ask for help is in the Atlassian Developer Community: https://community.developer.atlassian.com/ The mentioned portal was specifically created for development questions, where you will find articles and suggestions from other third-party partners…

Hello Folks, Additionally to the information above, we created a feature request to properly increase the limit for the MaxResults parameter in REST API: JIRA Cloud REST API increase the limit for maxResults Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Hello, Additionally to the awesome answer provided by @Yogesh Mude, you can also check the following guide with a detailed step by step to link Jenkins to Jira Cloud (Both Software and Service desk): https://confluence.atlassian.com/adminjiracloud/integrate-jira-cloud-with-jenkins-972355471.html

Hello @Jimmy Marchant Welcome to the Atlassian Community! Per your description, I understand you have configured an automation rule (Under project settings > Project automation) to create a ticket and update it with a request type, however, the mentioned error is returned to you. Can you confirm if you are using a Next-gen…

Hello @Elena Williams Sorry to hear you are facing a bad experience while creating tickets in Jira. Please, allow me to provide you with some details and concepts so we can confirm we are on the same page here: I can confirm to you that it is not a common problem in Jira to don't save a ticket when you have clearly clicked…

Hello @Deric Thank you for reaching out. The behavior you are describing happens because the board details indexes only when you first access it, so a refresh is required to display any changes performed in the detail view. In fact, this is not a defect but an intended behavior to prevent performance issues. That being…

Hello @wendy lim Welcome to the Atlassian Community! You can configure an automation rule to send daily notifications to your customer until the issue reaches the date provided in the Due date field. These would be the steps: * Navigate to your SD Project > Project Settings > Project Automation (Not Automation) * Click to…

Hello @Nicolas Karlinski Thank you for reaching out. The behavior you are facing when clicking to edit the Epic link field is a bug in the new issue view, which causes done Epics to also appear in that list with no option to hide them as we have in the create issue view. We created the following bug report to properly fix…

Hello @JJ Thank you for your answer. Can you confirm if there are any other required fields hidden for the request types where the error is happening? I believe the same problem is happening in these two request types too, however, may be another field can be causing it. Can you check if that's the case? Also, can you…

Hello @jeanette.wong Welcome to the Atlassian Community! Per your description, I understand you want to select specific fields to be displayed in cards (issues) of your Next-gen board. Is that correct? Unfortunately, It is not possible to edit the card layout of Next-gen boards at this moment. We understand how useful this…

Hello @[deleted] Thank you for reaching out. I believe there are no reported bugs that could cause the default priority icons to don't display properly, so I believe you are probably facing a cache issue in the application. I went ahead and cleared the context cache for your Jira application site. In order to check if it…

Hello @kiranmai genkolla Thank you for reaching out. Unfortunately, it is not possible to set project permissions (Create issues, edit issues, etc.) per issue types. We have already requested this ability with our development team before, however, they decided not to implement it since it would add more complexity and…

Hello @Victoria Santos Sorry that we gave you this perception and feeling about the Next-gen projects. Please, allow me to clarify some concepts so we can confirm we are on the same page here: Jira automation is not a functionality developed by Atlassian. In fact, it was developed by a third-party partner (Codebarrel) and…

Hello @jmarko Thank you for reaching out. Unfortunately, the customer portal does not support transition screens, so I'm afraid it is not possible to fill any fields during a workflow transition. We have the following feature request to get this option implemented: Allow Editing of Fields through the Service Desk Request…

Hello @Jason Brooks Welcome to the Atlassian Community! Since you have just upgraded your site to the Standard plan, I believe you might be in the trial period where the limit is still 100, as described in this documentation: Jira can send a maximum of 100 emails per day on the Free plan, then email notifications will be…

Hello @Anil Welcome to the Atlassian Community! The format of Jira notification templates should follow the same format specified in the look and feel of your Jira site, as mentioned in the documentation below: Configuring the look and feel of your Jira applications However, there are a few date fields that its formats are…

Hello @Sayaka Thank you for reaching out. By the description of your logs, it seems you are facing the same problem outlined in this question where the parameter of sql_mode is set to NO_AUTO_VALUE_ON_ZERO, causing the error you are facing. To fix this error, you can follow the steps below: * Stop the application. * Stop…

Hello @Roni Hoffman Thank you for reaching out. If the small requests worked through the week will impact the Sprint estimation and should be considered there, the best approach would be to create a new issue and add it to the Sprint with the amount of time estimated. Issues added after the Sprint start will be displayed…

Hello @shashi_prasad Thank you for reaching out. Per your description, I understand you want to search for issues in JQL, ordering them by the amount of time logged. Is that correct? You can achieve that by using the timespent field. This would be the syntax: ORDER BY timespent ASC P.S: the field above is only applicable…

Hello @tmanai Thank you for reaching out. I understand you are talking about the export options in the issue navigator page as displayed in the screenshot below. Is that correct? I believe there is no way to restrict the export options from the issue navigator page of Jira, so I believe you might be talking about a…

Hello @Marco Brundel Thank you for reaching out. I'm afraid it is not possible to add a whole group/role to the request participant field since it is a user picker field, additionally, I believe this is not a good practice. Allow me to provide you with some concepts to confirm we are on the same page: The request…

Hello @Paul_Scott Thank you for reaching out. The dialog box displayed when transitioning an issue is basically a screen added to the workflow transition, the same kind of screen configured under your project settings > Screens to View/Edit your issues. To properly add a screen to your workflow transition, you can follow…

Hello @Pedro Piovan Welcome to the Atlassian Community! I believe the best way to distinguish the issues from different clients would be by using the Component field: Organize work with Components Using components, you will be able to also define a default assignee and lead for each client you have. Additionally, you can…

Hello @Gianmarco Reverberi Thank you for your details. I'm afraid we will need to dig a little bit further in the logs to properly troubleshoot your issue. That being said, please go ahead and create an internal support ticket with us in the link below, properly pointing this community question and what we already…

Hello @support for vo I'm glad my answer has helped you. I'm afraid I don't have a definitive answer to your new question tough. I mean, by the scenario you provided so far, you can easily manage all your teams with a single Service desk project, using multiple queues and request types to properly differentiate their work.…

Hello @vshah Thank you for reaching out. Per your description, I understand you want to automatically select the Sprint for the new issue created with the automation above and transition it to a specific status. Is that correct? Since your rule will interact between two projects (A and B), you must create a Global rule to…