Petter Gonçalves Atlassian Team

Hello Jason, The warning returning to you (Yellow color) report anything that is not using the recommended configuration of JIRA SD, however, will not cause other functionalities to stop working or any further problems. That being said, if you really want to restrict your Agents from deleting issues, you can click on…

Hello Frank, I think that the best option for you in the scenario you mentioned is to use (Or create) two different issue types: Dev Task - When created by the Devs. Client Task - When created by the Clients. Performing the steps above, you will be able to configure two different workflows for the Issue types and decide…

Thank you for your feedback, @Rob_Hughes. I understand your point and hope that our support team will implement this functionality soon.

Hello Simon, Yes, your Customers permissions are properly configured, now you can add customers (With no Organizations) to your site and they will not be able to share the ticket. Now, I would like to better understand why you are using the Organization feature if you don't want to share your tickets? As mentioned before,…

Hello Anandaraj, As you can check in the questions below, it's not possible to hide this panel from the internal screens of JIRA since it provides you with necessary information (how the ticket was created and what's the request type).…

Hello Simon, Actually, the instructions you found are only to avoid the notification that is sent to the customers when the ticket is created, however, it will not restrict the ticket from being shared. The feature which gives your customers the option to share their requests with other customers is the Organizations.…

Hello Simon, I understand that you would like your Admins to be notified when a customer creates an issue in the customer portal, is that right? If that's the option you are looking for, you have two kinds of notifications on JIRA Service Desk Projects: Customer Notifications - Notification sent to customers with limited…

Hello Ashbal, The syntax of the query you are performing is working like this: - issue in commentedAfterDate("2018/10/19") - The issue was commented after 2018/10/19, however, not necessarily by the user Admin - commentedByUser(admin) - The user admin commented on the issue, but not necessarily after 2018/10/19 As you can…

Hello Chris, You can try the plugin Similar Issue finder which provides you the Similar Issues Tab on your issue view for a quick search in your JIRA: Also, you can use the own plugin to perform a global quick search if you want to. Please, let me know if this tool is useful for you, Chris.

Hello Mariah, The Epic Sum-up plugin can provide you with this information. Please, start a free trial and check if this is what you are looking for.

Thank you for the information, @changpeter_vmware_com Usually, post functions are not "Blockers" for workflows, but only validators and conditions can indeed restrict any transition from being completed. That being said, Although I'm not familiar with the plugin you mentioned, I believe it will not cause you any problems.

Hello, Can you please let us know what is the post function you are using? If the post function you are talking about is built-in JIRA (Not from a plugin), I can say that it will not cause any error when the field is not present to be copied. It will only not work, but the transition will be completed anyway.

Hello Madhu, The answer is no. Customers are not counted as paying users on JIRA Service Desk. You can add as many customers you want and you will not have any extra billing for it. P.S: Just make sure you are adding them as Customers only who can only access the Customer portal and nothing else. For more information,…

Hello Ivan, To display Done issues in your Backlog view you only need to edit the filter query of the board, as you mentioned that you have done. Once you remove the parameter that is removing the done issues from the board (Resolution = unresolved, status != done) it should be displayed on the board as any other issues.…

You are welcome, @Fr0zt. Please, let us know if this option has worked for you.

Hello Guido, You can configure Issue Security Levels to allow users to access only their Assigned tickets. Please, check how you can do it in the article below: - How to limit user to only browse issues assigned to or reported by them

Hello @Debbie Buswell, Thank you for clarifying that you are using JIRA Server. The condition I mentioned is only available for JIRA Cloud, however, it can be achieved on JIRA Server by installing the add-on Jira Misc Workflow Extensions.

You are welcome, Priyendu. I believe that Automation for JIRA is the most simple and straightforward plugin to perform this kind of configuration without needing any code, however, you can also try Script Runner if you are familiar with Groovy Scripts.

Hello Priyendu, Unfortunately, this functionality is not available on JIRA now, however, you can use plugins to automatically create sub-tasks when an issue with a determined issue type is created. Automation Lite for JIRA Cloud would be a good option to implement it, by configuring a rule like this: Please, let me know if…

Hello Debbie, You can use the Previous Status Condition to each transition in your workflow, so it will ensure that the last status that your issue was transitioned from is the same that it's being moved to. To do this, you must perform the steps below: - Navigate to your project > Project settings > Workflows - Click to…

Hello Maxim, That's a strange behavior. I've tested in my personal instance and I was able to delete shortcuts or any repositories added in this panel, even using a different user than the one who created it. Anyway, I believe that maybe some permission restriction or browser cache can be blocking you from deleting it. Can…

You are welcome, Michael. Have a nice week and please let me know if there is anything else we can help with.

Hello Ragan, For the Cloud platform, you're correct to say that we don't have a way to update the completion date since we don't have database access in Cloud. In fact, the completionDate of the sprints are not editable even using REST API (Refer to this link). That's why we created the following feature request: - Add…

Hello Rex, Jira Cloud for Slack (Official) allows you to integrate multiple projects to the default channel mentioned before, however, you must have the project Administration permission to perform such integration. I think that maybe you were facing some permission problems, that's why the projects were appearing greyed…

Thanks a lot for this useful information, @Nic Brough -Adaptavist- @saroja muninaga Can you check if you are able to build the script as you need with the code provided by Nic? Additionally, I would like to ask you again to also refer to the Script Runner documentation 

Hello, In your first sentence, it seems that you are looking for a way to transition an issue to a determined status when it is assigned, however, in your example it seems you are looking for a way to block issues to be transitioned to a determined status unless it is assigned. To automatically transition an issue to a…

Hello Saroja, I'm not aware on how to build a Script using Script Runner to achieve this functionality, however, I think That the analysts from Adaptavist (maybe @Nic Brough -Adaptavist-) Could give you some insights about it. Also, here's the ScriptRunner documentation: - Adaptavist Script Runner

Hello Rex, There two add-ons available to integrate JIRA and Slack: - Jira Cloud for Slack (Official) - This is the official Slack Integration provided by Atlassian and allows you to integrate all your projects to a single channel in your Slack Workspace called "jira". - Slack Jira Integration - This add-on allows you to…

Hello Saroja, You can use Automation for JIRA to achieve this kind of functionality: Please, let me know if this option works for you.

Hello Nate, Have you tried the Translation for Jira Service Desk plugin? I believe this add-on provides the functionality you are looking for. Cheers, Petterson Gonçalves