Marc -Devoteam- Community Champion

Hi @ckopanon No this can't be done otherwise, as the approval step on a status has defined transitions in the approval. Screens on these transitions won't show as the action by the initial approver triggers the transition and this gets executed. The only other option you have is to add the approvers when the work item is…

Hi @Noah Voerg and @Clairee Daniels Some 3rd party apps require this to be done, based on that information from the users Atlassian account can be accessed by the app. So if a users wants to use the 3rd party's app functionality (the app is installed on your instance), this question is being asked, before the apps…

Hi @PT I will not go into your language, but you are using a "Free" instance,. So you don't pay for nada, and you expect to get everything you want!!! That would be the same to leave your house open and you don't mind people stealing your stuff!

Hi @Ayla Atilio Florscuk Welcome to the community. In Atlassian Administration, under the settings of the site, within the option "Connected Apps" within the settings menu "User Installed Apps" must be set to "Allowed"

Hi @ckopanon Based on your information, is this an official approval step, based on accept or decline a transition is made? These transitions are made based on the action on the button on the portal or email, screens on these transition can't be used, as the action is done directly based on the chosen option. If you want…

Hi @ckopanon Are the people in the org admin group assigned the role Service Desk Team (agent license required) or Service Desk Customer

Hi @Rhys Duindam Some parts are still not translatable. Like "related sources" -> https://jira.atlassian.com/browse/JSDCLOUD-17969 KB categories, not been deemed to be done: https://jira.atlassian.com/browse/JSDCLOUD-8736 You could look on JAC for other related issues on your current non translatable topics.

Hi @Mads Illemann Then you will 1st have to bulk edit the issues reported by this user, to another user. Then you can remove the user.

Hi @Daniella Baaklini Best is to reach out to the support channel; vendor/developer of the app AssertThat. Maybe changes have been implemented in the app, or it's a bug.

Hi @Jonathan Porta As both apps are from the Marketplace vendor, it's best to reach out to Tempo support via their support channel. This might be an issue on you instance. Checking Tempo status, there seems to be an ongoing iss, https://status.tempo.io/ 

Hi @Kustagi Suma Work items of the same type are on the same level and can only be linked linear, they can't be linked in a parent child realtion. See issue linking; https://support.atlassian.com/jira-software-cloud/docs/link-issues/ Also please provide your current automation setup with detailed information about the…

Hi @Rhys Duindam Welcome to the community. Did you add languages to your JSM project, so request types will be translated. https://support.atlassian.com/jira-service-management-cloud/docs/provide-help-in-multiple-languages/ Also translation is also related to a users regional settings on a device or even the browser…

Hoi @Eric Roetenberg Die is er niet voor een simple Rovo agent, via studio. Deze communiceren binnen een work item. Dan moet je gaan kijken naar het toevoegen van een skill aan een agent. Of als je meer advanced wilt, moet je kijken naar het maken van een eigen agent in forge.…

Hi @Aditya Pramod You need to raise an issue via Atlassian Support, they only can remove the Rovo app. There is no other option at this moment.

Hi @Alex Cook If my answer helped you, please accept it as it might help other as well

HI @Patrick Geiger Contact the administrators of your Atlassian Cloud instance, if your account is managed. If not, see manage-two-step-verification-for-your-atlassian-account 

Hi @Kazuya Maezawa Welcome to the community. Your question could have better been asked at https://community.developer.atlassian.com/ You you should raise a requests via Atlassian Support, as this seems. to relate to an issue with your app on the Marketplace

HI @Alex Cook Yes, currently this can only be done using a space based on a company managed project. See this feature request for this functionality on a Team Managed project, https://jira.atlassian.com/browse/JSWCLOUD-22084 I don't see this comming soon, as screens are only manageable via Jira administration and not on…

Hi @Anik Chatterjee You are closing issues with the "bolt" icon, then this seems you trigger when the issue is already closed. What kind of property setting is there on the status "Closed" in the workflow? Can you show these details.

Hi @Eric Roetenberg You can built an agent with these pre-requisites, but you will still have tol tell the agent to create an issue at the end. Or see on putting this into the description of the agent, but then there is a risk that whenever using the agent it will always create a work item, on what ever answers will be…

Hi @Troy Anderson api.atlassian.net endpoint is of MCP/Forge, used with service account tokens, jira operations (alerting), etc.. It has the same options. Not all API endpoints can be used with a service account or scoped token. Mostly only API endpoints, specifically options need to be stated, it will show the…

Hi @Stephen Anderson Welcome to the community. When will a cloned ticket be created, is this on a specific action in the source issue? As based on the default Clone action if the original issue has a parent the cloned item will be linked to that parent. So how do you clone an issue?

Hi @jimmy pilon So you can connect from co-pilot to Jira now. But you don't get any Jira content right?

Hi @Donald Duck Try using {{issue.parent.comments}}

Hi @Alex Cook Use a transition screen on on the transition between statuses. Place the field "Change outcome" on the transition screen. Then on a transition between statuses this field can be edited.

Hi @Julie Santiago What happens if you switch it back to the original request type? Does this reconnect it.

Hi @Венера Welcome to the community. * No this is possible natively possible, but you would need to create a script that for each issue gets the issue id via an API call, then store the attachment id's and then call the API with attachments id's to get the files. Otherwise this would require scripting or a 3rd party app…

Hi @michelle_samaan Who is providing the error, Slack or Jira? If it is slack what is the full error, if that only shows "third_party_bad_request_error " then it's best to reach out to Atlassian Support or even Slack Support to get claritrty on the error. As this indeed shows little information.

Hi @jimmy pilon I'm not from Atlassian Support. This is a public forum with users like you that try to help each other out. We can't see any instance information, then you would need to reach out to Atlassian Support But try a simple action, use a full api or OAuth toen based on your own account and see if you can connect?

Hi @Moori Bakhtiari Currently it seems that this is not possible. You could reach out to Xray via their support, if you can join the closed Beta or see when this will be possible in Cloud.