Vishal Biyani Expert

Thanks @Charlie Misonne is there anyway to find out what the current value of X-Ratelimit-Remaining? when i print(session.headers) not getting this value till failure?

@Trudy P Claspill This is awesome. Works like a charm. I could use {{ issue.parent.key }} etc. to populate Initiative details at Epic level when subtask is created under StandardIssueType. Thanks so much for your patience and devoting your valuable time. It gives a great perspective and opens up so many possibilities to…

@Trudy P Claspill This is the rule i have I didn't think about Scheduled trigger. That surely will reduce the complication if Epic is prepopulated. However, would be good to know if they is way to update Epic if sub-task is updated.

@Trudy P Claspill My objective is to get initiative details populated at lower levels (Epic, StandardIssue and SubTaskIssueTypes). As per current scenario, it is possible that Epic and Standard IssueTypes under it don't have initiative details as these were already created. Now, i create a subtask under StandardIssueType…

@Trudy P Claspill This is very helpful and simplifies my logic. I recently added the custom field (custom_10300). This field is available at all issuetypes. I want to populate this field on issue creation up to epic level, if it is empty. So, if the trigger is sub-task, i can check for parent and update the field at…

We are starting to use JSM in our company. Any guidance on various best practices would be helpful.

@Bill Sheboy @Hannes Obweger - JXL for Jira Thanks for your inputs. I am able to make JIRA automation work correctly and rollup original estimate at StandardIssueLevel to Epic. @Hannes Obweger - JXL for Jira your screenshots were helpful to understand the mistake i was making. Now that JIRA Cloud is migrating to parent…

@Rajat Saxena As you are having premium license, you can define issuetypes and consider them at a level above epic. So if you create say Initiative, you can get hierarchy like Initiative -> Epic -> StandardIssueType (Task) -> subTaskIssueTypes In the parent field of Epic, you will need to specify issue key for initiative…

@Bill Sheboy I am using JIRA cloud. I tried to use lookup values. However, it did not work out. May be i am doing something wrong. The automation rule I wrote is: * When value changes for Time Tracking * For Epic (Parent) * Edit Issue Field (Original Estimate)* {{lookupIssues.aggregatetimeoriginalestimate.sum}} This does…

Anyone wanting to use JIRA automation can create an automation rule to update a custom field when Team field is updated. The rule could be like: When Team field is updated Then Edit issue field and update below rule in "Additional fields" { "fields": { "customfield_10111": { "value": {{ customfield_10001.name.asJsonString…

@Lali Your use case is there can be n number of tasks in an epic. If original estimate is added/updated/removed, then the updated sum of all the original estimates in the n number of tasks should get updated in epics original estimate field. The challenge with this use case is, JIRA automation using smart values does not…

@Jorge The solution is to use validator on Epic workflow at Create time. You need Jira admin permission and a workflow specific for Epic to make this work. See below screenshots

@Jorge The solution is to use validator on Epic workflow at Create time. You need Jira admin permission and a workflow specific for Epic to make this work. See below screenshots

@Kai Becker Thanks for your quick response. So the alternative solution will be to 1. check changelog and determine issuelink has changed (deleted) 2. compare source and destination and if source (e.g. database) has extra values for the particular issuekey compared to destination (latest API response) delete the extra row…

@Thuy Pham Thanks for sharing the link. The idea looks interesting. Will explore sometime later and see how this approach can serve the purpose

@Thuy Pham The solution that i came up with may not be optimal. However, it served the purpose. Jira Automation does not allow looping like we do in programming. So assuming you want to create a predefined number of subtasks below can be done: 1. On an event trigger the rule. I used issue transition rule. 2. Populate…

Yeah. JIRA Cloud retaining audit logs for just 3 months is on the lower side in my opinion. Now that i know, Audit logs are removed, will use REST API https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-audit-records/#api-rest-api-3-auditing-record-get to store them locally so that in future i have the…

@Vandana.Kareer You can use Post function to say "Resolution of issue be set to Done" Or you could throw a screen to user, where they can provide the resolution before moving to Done status.

Thanks Everyone for the response. I had checked in audit log and didn't find what i was looking for. Post your responses i checked and found the audit logs were set to retain for 3 months data only :-(. 

Is your Done status mapped to Done in workflow? It should appear as Green in your work flow 

@Carlos Faddul so would it be right to invoke below API to check if user is authenticated with help of rest API using below API? https://your-cloud-instance.atlassian.net/rest/api/3/myself

@Hamza Chundrigar Rolling up non standard values from Standard issue to Epic level is not feasible. Based on my research, rolling up story points at Story level to story points at epic level is possible using smart values. However, rolling up original estimates at Story level to Epic level is not feasible. What i did was…

Just in case anyone else hits this thread, what i ended up doing was expanding the json response using renderedFields. This gives description in html format. then use python library markdownify to convert the output to markdown syntax. It is working fine for my usecase

@Russell Brown Will this JQL work for you #1 project = XYZ and "Epic Link" = EPIC# and issuetype = Story order by rank ASC #2 For automation rule, you can try below. i have done it for Epic and related Issues. So if an Epic is Done then all issues under Epic are transitioned as Done. You can similarly do it for Story and…

@Renato De Araujo two dimensional Filter statistics is available as a gadget in JIRA dashboard. Take a look at this gadget and see if this works for you

@Renato De Araujo have you tried using two dimensional Filter statistics? For this to work you will need to have a saved filter query.

Let's connect over weekend

@Hemanth Lucky You need to use this API https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-worklogs/#api-rest-api-3-issue-issueidorkey-worklog-get to get all worklogs if the issue has more than 20 worklogs

You can refer to this link for illustration on how to use the API https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-post https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-worklogs/#api-rest-api-3-issue-issueidorkey-worklog-get

@Hemanth Lucky Looking forward to discus your doubts with you. Let me know your email id, and i will message you.