Marc -Devoteam- Community Champion

Hi @sujit kumar This call is not for setting information to be used in the UI in Atlassian admin. See this article; https://support.atlassian.com/user-management/docs/update-roles-and-properties-for-jira-users/ specific; "These user properties are not the same as the user properties accessed via the REST API." So the user…

Hi @Isabel Mendonça You will need to raise a support ticket with Atlassian, use the billing and account option. This as some apps can't be removed by yourself, like Rovo.

Hi @Jens Prokoph Check the screens related to the issue type used for this request, is the reporter field on the edit, craete or view screen? Other option, check the request type and the work item tab, is the field on the work item view?

Hi @Thomas Pedersen Ljungstrom No currently there is no option or work around for this behaviour. Also see https://jira.atlassian.com/browse/CONFCLOUD-78129 Other marketplace options might have this option, but I don't know any.

Hi @Alexandre Bonhomme As mentioned by @Arkadiusz Wroblewski is probably due to validation on the create transition of the issue in the workflow or related to the field configuration, based on required fields

Hi @Kelly Elizabeth Hutchison Can you try another browser or incognito window, does this improve the handling? If it does, clear your cache and cookies, also if browser add-ons are used, disable them it might be one on them causing the problem.

Hi @Emin Teoman Serim Yes, it will. The report based on the values in the sprint field will be impacted, if the values re removed.

Hi @Halil İbrahim AKCA Currently there is no work around for this issue. You could raise this to Atlassian via https://jira.atlassian.com/secure/Dashboard.jspa? 

Hi @Emin Teoman Serim This is strange, when where the issues creted, or where they imported, is there any information on the automations that might have caused this. Have the issues been moved etc. But your only options seems to bulk update these issues and clear the sprint field.

Hi @Thomas Pedersen Ljungstrom What if you change the JQL rule in your automation rule. Remove the .jiraDateTime() smart value options, to my recollection you can't use these in a jql. This as .jiraDateTime formats the value as text As based on your main JQL is is a date time field, so information is already set to:…

Hi @Support SPOC Welcome to the community. If your transition in the workflow has screen, you are not able to use bulk functions from the list view or all work view. Then you need to use the search option to find your work items and via the action (3dots) to the bulk action, as mentioned by @Trudy P Claspill 

Hi @Gerardo Saca This is still the case. If a service account can be used, there is an option named "Granular", just as you can see in the API scopes of the Jira Cloud API.

HI @Arthur Philip If I google this, this is a MS error, mostly in relation to outdated mobile apps. See some of the most likely causes here; https://www.errorsolutions.tech/error/office-import-error-domain-912/ 

Hi @박상욱 To me seems like this is impacted by a change made by Atlassian. As I have seen multiple questions on the same topic @Arkadiusz Wroblewski and @Trudy P Claspill I think raising an issue with Atlassian Support is your best option, as it seems it might be a bug due to an implemented change. The questions which one,…

Hi @Porzelt Dominik STAM Welcome to the community. You can go over this KB article, how-do-i-troubleshoot-errors-in-my-data Otherwise reach out to Atlassian Support, as they should be able to see this from logging on your instance.

Hi @Emin Teoman Serim Removing the Sprint label from the tasks. Can you see in the task history when the sprint label was added and by whom?

Hi @Mai Ashraf If my answer or answers of others helped, please accept them as a solution to your question, this could help others out and provides responders with gratitude.

Hi @Darryl St_ Pierre yes and thre configuration on the import on the assets schema

Hi @Chad Henderson I assume you are using a form from on the space setting in you JSM. You don't store this form checkbox field in a Jira field, but its just there on the form. Then see this article on how to get this information based on smart values.…

Hi @Ketan Gupta Then you can't use this in automation. You will need to map this field to a Jira field, as the smart value you want to use only works if this field "Email address" exists in Jira. Or you have to create a smart form, based on the form option within the space settings, then the inputs in the form can be used.…

Hi @Das Chebattina Please accept the answers from community members if they helped you out. This is useful for other users on the forum as well. Thank you.

Hi @Vaibhav Verma But this doesn't answer my question. Is the user already created in Atlassian before the user gets to the portal? Is the created user listed as a customer on the project before the user gets redirected to the portal?

Hi @PARISATO Marie-Hélène Oui, un problème peut être créé dans Jira via l'API. L'utilisateur qui exécute l'appel API doit avoir un compte dans Jira (licence) et accéder au projet Yes an issue can be created in Jira via the API. The user executing the api call does need to have an account in Jira (license) and access to the…

Hi @Brent Lee I also can't replicate this on any of the sites I manage or even my own free instance. @Mohanraj Thangamuthu I think it's best if an issue is raised on support, might be an instance problem.

Hi @Taylor Huston Yes, but this is unfortunate the only option you have. You can always disable the access again.

Hi @Maciej Baś I assume that the old inactive instance also has been deleted, so you can't disable this from the JSM side. I think you should see how integrations then can be removed from the Slack side, as the JSM instance doesn't exist anymore.

Hi @Dejan Welcome to the community. This is not possible at this moment, see open feature request ECO-1186 

Hi @[deleted] You will need to contact Atlassian Support Here on the forum we can't assist with these kind of errors in relation to your instance. @Florian Bonniec this is a typical cloud error message.

Hi @Vaibhav Verma If a user is not listed within Atlassian (user doesn't exist yet) they will land on the help center portal See SSO for customer only accoutn, https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-for-portal-only-customers/ 

HI @Sam Check the following, go to Platform Experience in Atlassian administration, then to Sites and select your site, this will transfer you to the site settings. In the site settings, select connected apps, in the settings option there, make sure User installed apps option is set to "Allowed"