Vishal Biyani Expert

@Luca Tuchtefeld are you using "compare two values"? please don't use issue matches JQL. that will fail

@Luca Tuchtefeld i am able to replicate your error with the 2nd control in the below screen shot. Are you sure you are using the 1st one shown in the screen shot i.e. compare two values?

@Luca Tuchtefeld Try using this, this works - i.e. {{smart values}} condition

@Saad Ahmad if you want to create epics (issues) in an existing project, then go to filter all issues, click on ... (ellipsis) and use the menu "import issues from csv" Looks like you have navigated from Import and Export -> External System Import

@Luca Tuchtefeld Can you share screen shot of the automation rule that you have written so far? if your objective is to check if the summary contains the sentence "Verification of correctness by Legal", why can't use an if block with contains conditions instead of a RegEx?

@Ankit kharola use this end point, with startAt=0 and maxResults=1000 https://your-domain.atlassian.net//rest/api/3/users?startAt=0&maxResults=1000 Say you have 1500 users. in the first call when response.json() length is calculated it will return 1000. 2nd call will be…

@Amanda S When using scheduled trigger, you need to specify JQL inside the Scheduled trigger form. Remove your if block.

@Chris Jost Below is the working code. You can adjust the message according to your need. You don't need to use issues.comments as you are iterating via issues already. The {{issues.size}} issues listed below <table border="1" cellpadding="2" > <tbody> {{#issues}} <tr> <td><a href {{url}}>{{key}}</a></td> <td><a href…

@Jan Voorsanger A) Does this even matter? Yes, setting the resolution matters in Jira because it determines how the issue is treated in various reports, dashboards, and queries. For example: * Issues without a resolution are often treated as "open" in filters and queries (e.g., in the "Open Issues" filter). * Setting the…

@Ankit kharola You need to loop through till you get 0 count for users. Assuming you are using python payload = {'startAt': 0, 'maxResults': 1000} while True: call the api end point Get number of users returned. if number of users == 1000: payload['startAt'] += 1000 else: break hope this helps

@JR85 is your hierarchy initiative -> Epic -> StandardIssueType -> Subtask? if yes, you can try below query (assuming ABC-1 is your initiative) project = ABC and issue in portfolioChildIssuesOf("ABC-1") or issue in (ABC-1) if not, can you share the issue hierarchy in your project?

@Matteo Pacenti You can use automation for JIRA. Sample rule Add an Action -> When Manually triggered Then create variable (say summary): And Add Edit Issue Field: select your custom field and in the text box specify {{summary}} let me know if you face any challenge

@Geoffrey Chapelle You can write an automation rule like this Add a schedule time trigger every Mon 11 AM along with a JQL Let me know if this works for you.

@Chris Jost Since you are using {{issue.comment.last}} inside {{#issues}}, that is one of the problems. if you take it out and have something like this, it works. <tr> <td>{{issue.comment.last.body}}</td> </tr>

@Rosalind Bird When you are doing the issue transition, you have the option of adding a post function. The post function gives the option, to update one field value from another. based on your problem statement, I suppose this will suite your use case. if you want to go with automation, can you share screen shot of your…

@Jeffrey_Denton I am doing something similar i.e. summing up hours at epic level. I am relying on below function so that a loop on subtasks can be avoided. Save the calculated value in a smart variable and then editing the custom field in epic with the value set in smart variable. {{#=}}…

@Ratih Ebtania did you check if all the subtasks are marked as Done?

since both Tests and TestPlan are standard issue, can you share a screenshot to show how Tests is included under TestPlan

@jeimi garcia lopez Hours logged under sub-task don't automatically rollover to parent (story). if the original estimate is added at sub-task level, then you will not see this issue.

@Sankaramoorthi Ayyappan Is "Test plan" and Test under one epic, if they are not linked with each other? testPlanTests seems to be available if you have xray plugin,

@Sebastian Krzewiński Makes sense now. Thanks for your time!!

@Sebastian Krzewiński I don't think so. i created an account on the free version of JIRA Cloud where no add-ons where present. there also i could see the option of Export XLXS (form data)

@Arunajyothi Samala on the status click on properties. if you set key = jira.permission.edit.group value = jira-administrators it will block others from editing the issue. refer Workflow properties 

@Martin Bayer _MoroSystems_ s_r_o__ Your guidance was very useful in getting creation of dashboard automated. Accepted the answer.

@Arunajyothi Samala 1) In workflow, Go to the status transition on which you want to prevent users from updating the field, click on properties and add below in key = jira.issue.editable value = false it will disable edit to all fields. Natively there is no solution (as far as i know) to allow edit to selected field refer…

@Martin Bayer _MoroSystems_ s_r_o__ Thanks. Based on your response, i debugged further and after fixing the issue related to payload, this works fine. Is there any place where it is documented what are the various propertyKey available for a gadget?

@Martin Bayer _MoroSystems_ s_r_o__ I am able to add "Filter Results" gadget using put method. However, I am struggling to add "Filter Counts" gadget. i am not sure what is the right payload to use. I tried using two calls with below payload for projectFilterDetails i used payload_value={"id": "11860", "type": "filter",}…

@Martin Bayer _MoroSystems_ s_r_o__ never mind. i had missed dashboard and hence was getting 404 :-( The issue is resolved now. thanks for your guidance though

@Martin Bayer _MoroSystems_ s_r_o__ i added the dashboard gadget using url = "https://your-domain.atlassian.net/rest/api/3/dashboard/{dashboardId}/gadget" got the itemId using = response.json()["id"] Now when i try to run below API, replacing dashboardId and itemId received from above url =…

@Charlie Misonne Based on the response on stackflow thread, looks like rate limiting values come only when we hit error Code 429 how to get rate limit values in JIRA REST API of /rest/api/3/field