Vishal Biyani Expert

@Radka Svobodova Can you check if you have automation rule running that may be causing this behavior? It is possible the actor in automation is your id and hence in history you are seeing as if you edited the issue. Try to disable all automations in your project and see if that prevents the issue from happening and go from…

@Fabian Gropp Trigger: Version Created Add Component Create page in confluence Subsequently you can refer to smart value {{createPage}} Can you see if you are able to make progress with this approach?

@Angel The default condition works in case of Standard Issue (Story/Task) and subtasks. It is not working in case of Epic -> Standard Issue There is no other native solution in JIRA (using automation to transition back the status is a complex process). If you need this to work for Epic -> Story then you will need to use…

Can you share the SS of your complete automation including how you are editing the field?

@Aditya Sastry Can you try using replaceAll(" ", "")? {{issue.components.name.replaceAll(" ", "")}}

@Amulya Sankara Can you check and confirm if the scope of automation is project level or global?

@Richard Furness Assuming your JIRA cloud instance is integrated with say O365, if admin implements the policy that re-authentication needs to happen every 24 hours, then it could be the reason why you are observing this behavior.

@Amulya Sankara Can you check if you are hitting the automation limits and hence the rule is not executing? Automation service limits | Cloud automation Cloud | Atlassian Support

@Vasilis Kokotakis As per below articles, this is the only endpoint for Universal Plugin Manager. How to Access UPM REST API for License Details | Jira | Atlassian Documentation UPM REST API - Universal Plugin Manager - Ecosystem Confluence As far as I understand, GET calls for JIRA REST APIs support Basic Authentication.

@pallavi raj This can be achieved using JIRA Automation. if you have not tried it, you can read through this link to get an idea

@Patrick McManus Could you try with below code and let me know if it works for you? I have added 2 lines highlighted in bold and modified jira_options to include verify=False dict value. from jira import JIRA import urllib3 urlib3.disable_warnings() jira_options = {'server': 'https://jira.<domain>', 'verify': False}…

@Christopher Perez is the dropdown in a company managed project or a teams managed project? Is it defined as a custom field on is this field a part of a form? if this is a custom field you can access the smart value as {{issue.customfield_xxxxx.value}}

@Rob Fields The 'Decline' status can be controlled by adding conditions to the workflow transition. This way, the option will only appear when specific criteria are met — or remain hidden entirely if you prefer to work through issues until approval.

@Madhavi Your ask is not clear. if you want to show the details from two filters separately you could use two separate two dimensional gadget in the dashboard. if you want to show the results from both filters then you could use an or condition say filter = filter1 or filter = filter2

@prakashgss Can you try with this script? The difference in calling is to pass the Authorization in header. $headers = @{ Authorization = "Basic YourPAT" } $response = Invoke-RestMethod -Uri "https://your-instance.atlassian.net/rest/api/3/myself" -Headers $headers -Method Get $response

@jeff_trotman have you associated the custom fields with your project screens? When you create or edit an issue are you able to add value (manually) to the custom field?

@Rebekka Heilmann _viadee_ I tried updating description using below and it worked fine. Can you share what are your rule in Additional fields { "fields": { "description": "Updating description using automation {{issue.key}}." } }

@Vladimir Cech in SQL comparing NULL (Empty) value with value may not give right results. Therefore, for specific use cases is EMPTY needs to be checked.

@Mar If I understand it correct, based on issuetype, you want to have values shown in the drop field. I don't think this is possible out of the box in JIRA. 

@lila Expanding on what @Mohanraj Thangamuthu has indicated, can you try something like below or whatever will be your separator { "fields": { "Discipline": "{{issue.Team (IP)}} - {{issue.Dependency}}" } }

@Barrios_ Angelly Automation has a limitation of not allowing nested branching. Do you want to compare start date and due date in the email action? if so, then looping through lookupIssues and checking if Start Date > end Date while creating email body is possible. Can you clarify on this?

@Ayush Gupta Can you make sure you are clicking Add button and then save for viewers and/or Editors?

@Madhavi This is not feasible using native JQL as it does not allow subquery.

So, if you have existing group, add that in the filter and that's it.

@Ferry Portier You can create a custom field of type user picker (single field). Then it can be configured to filter out based on your criteria (either a group or Project Role)

@Osama Al-Areky are these under the section hide when empty?

This is something to do with data center version. Probably rest/api/3/myself is not supported

@Jeel Can you try to pass PAT in the header as part of your json payload? Authorization: Bearer <PAT> See this link for more details Using Personal Access Tokens | Atlassian Support | Atlassian Documentation

in JIRA DC, as per documentation i didn't see asNumber. if below gives empty result, then try without asNumber and see if it works {{now.format("d").asNumber}}