Marc -Devoteam- Community Champion

Hi @Habib Memon Make use of a Security Scheme in the related JSM project. Set security level and set a level for the agents from the 3rd party to only be able to see issues, with a specific security level. See the link in @Mikael Sandberg reply.

Hi @Ada Mu Contact Atlassian Support on the issue. Or is there an issue with your internal mail server, is normal mail being received?

Hi @admin11467 These option is also available on a free plan. Just tested this.

Hi @Angel Salazar Customers can only raise issues via the portal only Request Types are visible on the portal, so each issue created via the portal will have a Request Type set. Only agents could raise issues from the backend via the create button, then create an automation rule that if request type = a then request type =…

Hi @Kauana Rodrigues dos Santos As @Trudy P Claspill mentions this can be done. But you can also use the previous status condition on the any transition. Example:

Hi @Prasad Bonthu Can you share the postman workflow?

Hi @Ugo Abate If you use fields on an issue with dates, or sprint dates you need an automation rule to copy these values to another field. this field can then be used as the persistent date

Hi @Lucas Linzmeier On your JSM project, are you positive sub-task is on the issue type scheme used, can you show a screenshot?

Hi @Ugo Abate As you mention on @Jeffrey Wolfe , can you show the automation you have setup. Please mind the following: 1. what type of project is this (e.g., company-managed, team-managed, etc.), 2. images that show your complete rule. 3. images showing the details of any relevant actions/conditions/branches. 4. images…

Hi @Giulio Pengo This appears to be an intermittent defect, as described in the report below, and which is closed as "won't fix". The workaround is to have your Jira Site Admin create the rule from the global rule area in Jira. AUTO-643 

Hi can you show an example by using screenshots

Hi @rta Welcome to the community. What kind of permission does the account have? I might need admin permissions on Jira

Hi @Ugo Abate Welcome to the community. When using Jira Plans and you change dates, you need to save than changes made in the plan to the issues, The button is in the top right corner, you will need to have the correct project permissions on the issues you want to change. Or is this not your use case?

Hi @Timothy Johnston Welcome to the community. Can you provide some more detail, screen shots. I can still upload space export in my instance and other instances I manage.

Hi @admin11467 Welcome to the community. On the project in project setting in custom notification settings, edit the main template to remove these links.

HI @Stuart McNaught I would say raise it via https://support.atlassian.com/contact/ and see if it will be classified as a Bug

Hi @Stuart McNaught With the current product design, it is expected to add the Original Estimate only once, before any time is logged. For detailed explanation on this, please review the explanation shared by the product manager on this suggestion ticket: JRACLOUD-77064

Hi @Seenivasan K In a JSM project type it is not possible to use field layout options. I suspect that is what you want to accomplish?

Hi @Jayanth Looking at you payload and the API documentation you need to use { and } not [ and ] See, api-rest-servicedeskapi-request-post 

Hi @Lucas Linzmeier Sub-taks can only be created under a parent issue. So this also applies in JSM, you can create a sub-tasks under an Incident, Service Request etc...

Hi @Evert Morren Atlas Admin The smart value to use information from a form, when the the form submitted trigger is not used. Example if the smart value {{issue.forms.<uuid>>.last.FCM-Feedback reçu par}} equals whatsapp. The uuid of the field in the form can be found using the forms rest API…

Hi @Charlotte Reynolds Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same.

Hi @Ronnie van Gelder Please accept my answer as a solution, if my answer helped to solve your request. This will help other community member trying to solve the same.

Hi @Akash Check what the issue can be as the Google API is giving the 302, what does that mean on the Google API site. Is there a requirement for authorization headers maybe?

Hi @Angel Mosqueda Why use scriptrunner, this is an ootb function. https://support.atlassian.com/jira-software-cloud/docs/move-multiple-issues/ You could ask the app support department, but probably its not a function on the app as Jira offers this ootb

See the Jira issue that is linked in my previous reply. This is what your are running into. What if you remove all your pinned fields and then try or is this field from a 3rd party app as these fields can't be pinned. Does it work in another browser or incognito window?

Hi @Dániel Vincze Welcome to the community. The field issue priority is a field on the request, but is the the Jira field priority? Because this is where the SLA is responding to. I think you have a custom field issue priority setup, you should use the field Priority.

Hi @sindiso.luphahla The error in your screenshot explains the reason why right, unpin a field first and then you can add the field as pinned. Pinned fields are personal, but the issue there is whit this there is no exact limit on the number of fields, but it's limited on the number of characters, see JRACLOUD-78946 

Hi @Akash The 302 is coming from the Google site. I suspect it has something to do with not providing the correct Headers. In your rule also see them greyed out, if you need to use headers, even if the same as the greyed out, you will need to provide them.

Hi @Jürgen Hauck Welcome to the community. This based on the External user policy setting in Atlassian administration. It seems your account is part of this policy. Contact the org admin of your cloud instance.