Kai Becker Community Champion

Hi @Muhammad Ali Khan thanks for the question. The only solution for this would be the creation of Atlassian Accounts with this distribution groups. This comes with the tradeoff that you will have to pay for these dummy users too.

shared 🙌

Hey @Natalia Matsyuk , do you clone issues via an automation rule or just the regular Clone entry in the ... menu? Could you post some screenshots of the process? If you are using any automation, please post a screenshot of the corresponding rule. If none of this is the case, I would suggest opening a support case, like…

Hi @Maureen McKeon a field name can not be changed via a field context. This is simply for having different options per project in a single field. If you need it to have another name you will have to create another field or go with the new name in every project, as @Nicolas Grossi mentioned.

Welcome @Vijay Dadi 

Hi @Emilia KASPRZYK thanks for clarification. As far as I know, there is no solution to let the customer pick his agent. Sorry...

Hi @Emilia KASPRZYK thanks for your question. What do you mean by "choose assignee by customer" ? Regarding the options for the customer to reject or close a ticket, you have to go into the workflow of that request type or its corresponding issue type and make sure to enable the checkbox on these transitions:

Hi @Xitai Liu welcome to the community and thanks for your question. There is no such thing like free Jira community edition you may know from other software. But, if you are an qualifying nonprofit that is non-governmental, non-commercial, and non-political, you can apply for a community DC license…

Hi @Dinonath Khan thank you for your question. To clear things up, these are two different products and they share different user roles. I'll try to explain as simple as possible: Jira Service Management * Customer = A non licensed user, who is only allowed to raise requests via the portal or email * Agent = A licensed…

Hi @Rajat Samseriya I don't know of any documentation directly for this use case. But I will add a few for the seperate steps: You can follow this documentation for creating a new custom field: https://support.atlassian.com/jira-service-management-cloud/docs/add-a-new-custom-field-to-a-project/ This guide helps you…

Hi @Rajat Samseriya welcome to the community and thank you for your question. There are several ways to implement this. I would usually go with a workflow transition called escalate, which then sets a field e.g. a label or a custom field for the 2nd level support. This can be filtered in the queue and displayed to the…

As Rajat is on Standard plan, he will not have access to Assets.

Hi @Meet Darji thank you for your question. Just one thing at the beginning: why don’t you JSM directly on your website? https://support.atlassian.com/jira-service-management-cloud/docs/embed-a-widget-onto-a-web-page/ The issue collector is a pretty old way of getting user feedback. It was introduced long ago since there…

Hi @Rizwan Siddiqi welcome to the community and thank you for your question. We the newly updated, now free Atlassian University, I would highly recommend starting with this learning path: https://university.atlassian.com/student/collection/850385/path/2753072 It will give you an excellent understanding of Jira and its…

Hi @Lee MacPherson welcome to the community and thank you for your question. A detailed guide on how to add new custom fields on DC can be found here https://confluence.atlassian.com/adminjiraserver/adding-custom-fields-1047552713.html But as you mentioned you asked your admins regarding the setting, I think you will…

Hi @Alexander Westergård thank you for your question. The possibility to find users is controlled by the global permission Browse users and groups This can not be changed on a project base. But I'm not quite sure if I fully understand the problem: Do you have customers using your JSM projects with agent view? If so, this…

Hi @Samantha Johnson welcome to the community and thank you for your question. You should be able to convert the string from the text field to a number with the following syntax: {{issue.YOUR FIELD.asNumber}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#asNumber If it still does not…

Hi @Willian Pereira Da Cruz Lemos welcome to the community and thank you for your question. As you are using Jira Cloud there is no possibility to directly connect to the database. This is only possible on the DC version. The Cloud infrastructure is different and not reachable from an end user perspective.

@Rompicherla Kalyani did you check the layout as mentioned?

Hi @Vijay Dadi did you also check to modify the issue layout to display the fields in the respective areas? https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/

Hi @Jesse Ortega Jr thank you for your question. Currently there has not been any update on this. Since you as a customer are responsible for backups of the entire site anyway (Atlassian only provides for disaster recovery), I would strive for a complete backup solution. There are several options for this in the…

Hi @Rompicherla Kalyani did you configure the issue layout and show the field on the context area? A detailed guide can be found here: https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/

Hi Filip, welcome to the community and thank you for your question. You should be able to solve this via Automation rule: The smart value {{changelog.Rank}} will be not empty when the issue has been reranked on the board.

Hi @Yousuf Al Rawahi thank you for your question. That's actually a perfect scenario for using workflow properties. These can be added to the DONE status and will prevent the issue from being edited.

@Nikola Perisic yeah could be. probably some sort of first come first serve issue. Glad you figured it out :)

Thanks for the update. If the condition is not matching, it could be a timing issue. You could try to re-fetch Issue data as action, before the condition. As there are two conditions, which one fails? Type Email Requests might be a problem, as I think it is the fallback for emails sent to the mail handler and might not be…

Hi @Viktoria Roussina welcome to the community and thank you for your question. When installing the app, you will get 30 days of trial usage. After that, the credit card you use for your site will be charged corresponding to the user tier of the product. As the app you choose is valid for Jira and JSM, it will be billed to…

Hi @Nikola Perisic could you give a little bit more detail on the fields? * What type of field is the Watcher / CC? Text, User picker? Multi or single user? * How do you edit the Request participants? Add new values? Set field to value from Watcher / CC? Does the participants field change in any way? For example will…

Hi Nico, thanks for your question. This is the expected behaviour. The preload of such dropdowns is limited to 25 entries. If you need to dig deeper you need to search via auto compete.

Hi @Tarek Faham closing a ticket should not result in "hiding" an issue. Could you clarify where you are trying to find it? On a board? In the issue search? If you are searching, could you paste the JQL/search term you used?