Marc -Devoteam- Community Champion

Hi @Злата This is correct, as this information is shown baaed on an inserted iframe. Automation can't read this, so this is not possible with automation. You would have to have a custom field, where this status would be reflected, then you can use this in a condition.

Hi @carolina.mendes No, as the markdown is taken into the change. The only option is to not use makrdown.

Hi @gollapudi sidhvi They need to access there issue via the portal. Yes, only if you store the information from the form fields in Jira fields

Hi @govindaraj.p Try the options on this KB article; troubleshooting-two-factor-authentication 

Hi @gollapudi sidhvi Yes, you could create a fomr for this and add this to the request on Closing it. This form will have to open so customers can edit it. I would add an extra status to the workflow, that if this form is updated, the request status updated to a non-editable status, like survey form submitted.

Hi @Ashutosh Upadhyay Please provide more context, where where the links added and whoat stpes did you take. Provide screenshots if possible.

Hi @Злата Jira automation can work with UI fragments. If you get the issue information via API, is there any information related the Gitlab status? It als seems this is provided via a 3rd party app, is this the case?

Hi @Achim Hepberger Reach out to Atlassian Support, via account option to report this. If the badge is not showing within a couple of workdays.

Hi @Sumathy_Subramanian In what relation are you asking this, based on a Test app, what App. If it relates to an app, you might want to reach out to the support channel of the vendor/developer

Hi @gollapudi sidhvi See the options, https://marketplace.atlassian.com/search?query=survey&product=jira-service-management&hosting=cloud and try them out in your sandbox, to find the one that fits. I have never liked one of them, so no preference here. And I think they are expensive.

Hi @jyoti_suryan Welcome to the community. What do you mean by status changed, to another status or the naming. The 1st should be visible in work item history. The 2nd, then an admin changed status names in a workflow and has not have the knowledge that this impact is global. Any workflow using the status that was renamed…

Hi @James Rickards _SN_ Does this involve the "Related Work" section. This is a rolling out feature. This has als been in the latest update, https://confluence.atlassian.com/cloud/blog/2026/02/atlassian-cloud-changes-jan-26-to-feb-2-2026 

Hi @Ian Araya Where you using a Free subscription of Jira and didn't you or anyone in your Organisation use this for the last 60+ days. The org admin of the instance should have received email (multiple) on non usage and that the instance would be suspended. Are you org admin, if not reach out to the admin or your internal…

Hi @michael_leyderman Welcome to the community. There are multiple PowerBI connector apps, which app are you using and what does their documentation provide?

Hi @gollapudi sidhvi No ootb the only option is to change the question. For expansion you will need to revert to 3rd party solutions on the Atlassian Marketplace.

Hi @KC Wong Created, Updated and Resolved, only work with day (d) parameter. So you can use "created >= "-365d"

The token you already use, did you convert this to base64? No typing it like this in authorization doesn't make it base64. Convert your created api token related to your email, for example here; https://www.base64encode.org/ On this site input my email:my API token, the result should be set as Basic result in the…

Hi @Sai Prabhakar Varanasi Are the users part of the group jira-servicedesk-users? Be aware you can only have 3 agents on a Free subscription. within administration, can you check the Billing option and see how many users are listed under JSM. Or provide screenshots?

Hi @Sam Thornton As I can see and tell on using the same features on an instance, this looks as expected behaviour. I do think it relates to using a behaviour as fields not using a behaviour can be edited inline. So it might be worth contacting Adaptavist (Scriptrunner) support on this. But I think this is based on how the…

Hi @Tejas Patil I don't think this is possible, as there is no dynamic lookup in automation. Based on how many possible combination are we discussing this. You might can create a lookup table based on possible option and create an issue based on the lookup table value to fill the component field. @Bill Sheboy any thoughts…

Hi @Ashraful Islam Welcome to the community. This is policy, to be able to revert mistakes made. I have asked for an Atlassian Support agent to look at your request, this can take up to 2 working days.

Hi @Melissa C If my answer helped you, guided your to, or provided you with a solution, please accept my answer. Also to provide other users with a solution, asking the same quesiton

Hi @Judy Colonero If my answer helped you, please accept my answer as a solution, also for other community members with the same question.

Hi @Dan Spearing Your Story is Child of an Epic. The ootb field Epic link in your instance seems to have been renamed to Feature Link (this is a decision made in your company instance) So Feature Level in your hierarchy is linked to Issue Type Epic So within Feature Link field you can select items from Story level. On an…

Hi @Rejaine Lima Please accept my answer if this helped you and to help others with a like question.

Hi @Vina Wu Change authorization value: to Basic and your key, als add key Content-Type and values Application/JSON, also for Accept. The greyed out options are not taken. See my screenshot. There is something wrong in your web request details, as the browser provides feedback correctly

Hi @Ioannis Xanthopoulos Please reply in the thread, instead of starting a new one. As I mentioned, as the documentation does mention this, but if you can't seem to use it, reach out to the support department vendor/developer of the app. Link is in my original reply.

Hi @Annu T Satpute Welcome to the community. Best is to raise a support issue around issues with your account. Check this article https://community.atlassian.com/forums/Community-Announcements-articles/Usernames-privacy-email-changes-alter-egos-and-you/ba-p/1056964 @Monique vdB could you help out?

HI @Melissa C In you jira workflow you could transition an issue to a certain status "ready for approval" and use an automaton rule or webhook to trigger an action in SN, that the SN ticket goes to an approval state Just a quick brainwave.

Hi @Yannam, Pavan (P.) It seems there is no column for issue type in your CSV, or there is but this isn ot mapped when importing the CSV