Jehan Bhathena Community Champion

Hi @Abhishek Kalamkar , for the "My Organization" Query would recommend creating a new question, since the main threadis already addressed in the current thread. With a new question you're more likely to get more inputs. 🙂

@Abhishek Kalamkar Glad to know it works. For the "My Organization" part, I didn't find any direct setting for this but the below workaround should suffice: * Create a filter manually with the required permission * Using the…

Hi @Mohammed Haneefa Farook , are these users from your own domain? If yes, have you claimed that domain in Atlassian's admin settings?

Hi @Matharoo_ Daljeet singh , There seems to be an option to fetch comments https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-comment/#api-group-comment Is there a certain use case you're trying to achieve here? Maybe that will help us understand the scenario you're trying to get to.

@Abhishek Kalamkarbelow is the Body you can use with this API https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-post, you dont need to create a new webRequest { "jql": "<JQL>", "name": "<name>", "editPermissions": [ { "type": "user", "user": { "accountId": "<<account ID>>"…

To edit the filters owner and editor you need to add the "sharePermissions" In the body of the request. You can find that in the documentation here : https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-post

Hey @Ben van den Berg , thanks for the update. I understand that Jira's smart values don't have it all, but from a product's perspective I don't think a lot of users would want to pipe all the history into a Smart Value (would be a huge value to handle) Think of the Jira API as an inbuilt extension to the Automation :-),…

@Abhishek Kalamkar , you cannot validate a request that uses a smart value. For {{webResponse.body.description}} to be resolved the first Webrequest needs to be fired, once done, the next request will use the output from the first request in the body. As of now, you're trying to send a empty value in your request that is…

Hi @Abhishek Kalamkar , As shown in your image This webrequest should work (in theory), do you get any error? What is not working in this use case now? Also, as a request please use the individual thread for responding to each response, so that we have a more clear line of reasoning. :-)

Hi @Mohammed Haneefa Farook Pls can you provide some more details about the users that are onboarded? Are they from your own domain? What details ar you trying to update via the api, and any error that you got when you tried this previously

Hi @homesfy987 , Those tabs are a result of an additional add-on for Git. You can try https://marketplace.atlassian.com/apps/1221011/gitlab-for-jira-cloud?tab=overview&hosting=cloud Or https://marketplace.atlassian.com/apps/4984/git-integration-for-jira-github-gitlab-and-more?hosting=cloud&tab=overview From what I know…

Hi @Abhishek Kalamkar As @John Funk rightly mentioned this cannot be achieved out of the box, since the {{version}} is limited to provide only the version name and version ID. In theory you can do this as a workaround : * Use the Below webrequest to fetch the newly created versions Note: the Delay further requests option…

Hi @Ben van den Berg , Didn't find a way to get this via a smart value or in simple human readable format. But you can try to use this API in the automation rule, and send the content from the response in the mail.…

Hey @GREY Stuart , Glad to know you were able to work out a solution. Would be great if you can mark the thread as accepted so it gets identified as a valid answer.

Hey @Gary Spross , if the above workaround helps pls mark this thread as the accepted answer, so that it can help others identify this thread 🙂

Hi @Peter Aldana , as the error states the connection fails due to 401 Unauthorized error, you may want to check the setup once more to verify this, do check the token/password timeout or validity, perhaps your token loses validity after a while and your connection becomes unauthorized due to that. Although if you're sure…

Hi @Sam Hayes , few things that you can try: * Can you try editing the Description manually in the issue view and see if it gets reflected? * Do you by any chance have another custom field named 'Description'? * Try removing the special effects i.e. the color and heading syntax and see if that works?

Hi @Shubham Rawat , As per the error you've mentioned, you can try to add yourself as a member of the site-admin group. Once added retry the connection via the plugin. Note: there is a new change coming where the org-admin is no longer added by default to all sites as the site-admin, not sure if this has been released and…

Hi @Krishna Chaitanya , Unfortunately we cannot work make the LOCKED field mandatory via the field configuration. In theory, these workarounds can be tried (not tested) : * In any workflow transition where you need that value, use the "Condition" to check if that value is not EMPTY * Or add a Automation rule to add a label…

Hi @Emery Manayan , Do let us know if the regex worked for you. Also, if this answer helped you, would be great if you could mark the answer as Accepted.

(?!)(zurich|sunlife) this is what you need to use. It works when I checked here : https://regex101.com/r/8wgXqx/1

I've checked this at my end too. You need to make the regex case insensitive, adding the syntax below. (reference : https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Regex-format-for-case-insensitivity-in-Automation-for-Jira/qaq-p/1446866#M74007) Below is the condition you'd want to use: Hope this helps :-)

Hi @Emery Manayan , Please can you elaborate what isn't working in the above automation? As per https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#Advanced-compare-condition, you have used the correct regex. Although I see that you've used Capital alphabets in the "Regular Expression" field,…

Hi @Bonita Christy , I haven't used JIRA Product Discovery yet, but assuming this uses the Same permissions as Jira's Global permission you may want to check the below permission: https://{your-domain}.atlassian.net/secure/admin/GlobalPermissions!default.jspa

Hi @janvolkert , You need to get in touch with the Atlassian Support team and raise this request with them. Not sure if they can help you directly, they need usually ask for permission to Access Site via the ticket and once the permission is granted they might be able to make the changes needed. (Assuming they can help,…

Hello again, The closest I got to this was tagging the initiator in the message. Fetch the User ID using Slack's API, then pass the response to the Jira WebRequest (instead of the Slack Message action) Hope this helps :-)

Ironically I haven't used Slack (ever) 😅 I'll give this a whirl on my instance once and let you know if it works.

Hi @Alixanne FERAUD , For the first question, you can print out all the values available in {{fieldChange}}, this way you can see if this prints out the Custom field ID or perhaps the name of the field that you are looking for. For the second question I would recommend starting a new tread it is better to keep this thread…

Hi @Gary Spross , I haven't tested this out but in theory you can try add 2 actions in the automation you mentioned: * Create a lookup table with Jira User's allowed to run the Trigger, along with their Slack Profile ID's :…

Hi @John Roberts-Davies , Checked this at my end too, seems to be working correctly. Would recommend checking this in scenario in your browser while in "Incognito". This is to verify if your browser cache isn't causing this issue. (usually happens a lot while I use Chrome browser)