Vishal Biyani Expert

@Hemanth Lucky Below is the high level approach i used, 1. I used below end point to get 100 results at a time and looped through the result set. /rest/api/3/search 2. Check if issue['fields']['worklog']['total'] > 20: Then use /rest/api/3/issue/{ret_issue['key']}/worklog end point to get worklogs starting from 21st record…

@Sreenivasaraju P Thanks for your response. I am cloud instance. When i check against an issue. This is what i see. Internally will JIRA be saving the time in UTC?

@Jimmy Seddon Could you elaborate what exactly you changed in your intake process? You also mentioned about estimation. Is there any specific methodology that you follow? These are the challenges that i am trying to address with my team. It will great to hear more from you on these points.

@Arthur Stepanyan Also, if there is a possibility of re-opening the tickets in your transition i.e. from Done state it can be moved to say 'Open' or 'To Do' then ensure that in the reopen transition the resolution is cleared using the Post Function. if this scenario is not taken care of, then quite a few JIRA reports…

@Michael Marriott Thanks for your feedback. Considering these complexities, i went ahead using python + JIRA REST API to read the summed up original estimates at standard issuetype level and after doing the calculation in code update the respective field value in the epic. this helps avoid taking care of lot of scenarios…

@Michael Marriott Thanks Michael for your solution. This is really helpful

@Mithila N Bhat This can be easily done using Jira automation and a custom field. I had a similar use case. My transition is open -> In Progress -> Fixed -> Open open -> Rejected -> Open If issue moves from Fixed to Open, or from Rejected to Open, count the # of times this happens and increment the custom field to count…

JIRA rolls up the time entered at subtask level to standard issue type. That's what you see when checking the check box. say 16 hours or effort estimate is entered at Story level if 8 hours of effort is entered at subtask level, then without the check mark you will be 16h remaining, while with the checkbox, you will see 8…

@benury Can you share the screenshot for history tab? if it was saved and then removed, may be change log can give some clue

@[deleted] This is because you have include subtasks ticked. If you uncheck this box, then see if time tracking still showing erroneous results.

Are you on Jira cloud premium version? if so, you can try looking at Advanced Roadmaps Otherwise, there is a plugin available in excel that can download data from Jira and you can create dashboards. The data source remains Jira so you don't have to manually populate the data.

@Pramodh M Thanks for your quick response. Question is How to parse though content node? Do i need to create a custom json parser that reads through all the content nodes? if so, when i hit say Node - hardbreak, what needs to be done to convert it to markdown syntax? or when Node - table comes, what needs to be done to…

I had been working on creating a JIRA dashboard using Python, Plotly Dash, JIRA REST APIs for my reporting purpose. This development saves me from relying on any plugins. The dashboard is shaping up really well and i really admire the way visualizations have been made feasible by open source Plotly Dash libraries.

@Sanket Sutar Vishwas has shared a Unix script with you. if you are on Unix/Linux system, you can use cat <filename> to see the output.

Looks good. Just make sure that default unit of time tracking is minutes. Jira admin can check this settings -> Issues -> Issue Features -> Time Tracking if this is set to hours then change the division from 3600 to 60.

Let me try to elaborate a bit more. There is No need for JQL, if you are interested in Time tracking changes. When the rule checks for "Value Changes for Time Tracking" it will get fired when time is logged against any issue in project. You can include the event. I had selected "Create Issue" and "Edit Issue" see the right…

@Faizan Iftikhar You can write an automation rule by checking if Value changes for Time tracking. After that you can put the numeric condition to compare if total time is > then your threshold, then use New Action to trigger Email action. I haven't tried this... but this approach should work.

@Michael Rans Jira uses markdown syntax for table formatting. There are online tools available to convert excel/outlook tables to markdown syntax. Of course, if your data is sensitive, this option will not work. From this post in stack overflow, i see one of the responses talks about a plugin for outlook to convert the…

@Bill Sheboy Thanks for pointing this out. I have rectified this mistake. However, not able to meet the use case as detailed below Under Epic, i have Stories, Task and Custom Standard issue time (say Use Case). We have created custom fields at Epic level Field Name: StoryEffort Field Name: TaskEffort Field Name:…

@Hana Kučerová Thanks Hana. This is exactly what i ended up doing this. So if issue search returns, total records in worklog as say 38, i am firing the Get issue worklog to startAt 21 and get the remaining work log items

If this is a Text field try using ~ operator to compare this with part values.

@Gustavo Miller For the REST API calls, you need to pass in the authentication details in the payload. from the code snippet, it is not apparent that you have passed the authentication creds (username, password/API token) The error denotes that you are trying to access the link with anonymous user and this operation is not…

@Ste Wright Thanks for your response. The structure that i am using is: Initiative -> Epic -> Standard IssueType -> SubTask Issue Type. I search the sub-task issues under Story as you suggested. I have 4 subtasks underneath the Story. Added Progress column in results window. What is notice is - * All the sub-tasks are in…

@Dario B Thanks for the details. This is preciously what i was looking for. Only issue is instead of accountid if this could take email id, that would have been much simpler to code

Thank You so much. Truly appreciate the time you have spent in responding to my queries. it has been really helpful in clearing all my doubts.

Thanks. One option to update remaining estimate is while creating work log entry. I tried to see if it is possible to update remaining estimate via Bulk estimate. it does not look like it is possible. Is there any other alternative approach to update remaining estimate?

@Nic Brough -Adaptavist- - I was under the wrong impression that remaining estimate is a field that is auto updated and should not be manually updated :-( Thanks for clearing this out. To Summarize: 1. Original Estimate updated as: 10 hours 2. Actual Time entered: 12 hours 3. Developer estimates that it will take another 3…

@Nic Brough -Adaptavist- Typically, to calculate Effort variation, we will see how much effort has been spent on top of effort estimate provided. But looks like if we need to ensure Progress % is correct, when OriginalEstimate is less that Actual Logged effort, we will have to revise the OriginalEstimate entered upwards.…

@Bill Sheboy Thanks for detailed response. I was able to extract "Status category change date" field in API call. It actually populates the date when issue has moved from To Do to In Progress, In Progress to In QA etc. What is not clear is how to use this field to calculate % Completion. Could you elaborate a bit more on…

@kai Thanks for your response. However, if I give 10h for Original Estimate while uploading CSV file to bulk create issues, it is failing.