Also included in the article is a way to quickly identify and surface issues that are affected by these limits right on your dashboard:
It's a custom report built in Report Builder, which means its source code can be modified to any requirement you or a client might have (more details in the article):
This report is not part of the app yet, but you will find a guide on how to add it manually in the article. Or just let me know and I will help you do that. :)
Atlassian Team members are employees working across the company in a wide variety of roles.
August 31, 2024 edited
@ting_t_chi if you're using Tempo timesheets, we recommend using the solutions and API provided by them. The subsequent community post includes the link to their solutions.
I'd like to commend @Shiraine Liu, @Apoorv Aggarwal and the Atlassian team for listening to user feedback on this issue and coming up with a workable solution for moving worklogs with Tempo. I haven't started using the new tools yet, but I feel much more confident that there is a path to resolve this without a major impact to our business.
We generate reports using Jira APIs in Power BI and eazyBI, while also using Tempo for logging timesheet. I would like to understand how issue limits could affect our operations in cases mentioned below:
What happens if an issue crosses a certain limit?
For example, if an issue has 2,540 comments, will it stay as is? Can additional comments still be added, or is there a maximum?
Will Jira prompt us to create a new issue to continue? If so, is there a quick way to create a new issue that replicates the details of the one that has reached its limit?
Is there a way to query issues to identify those approaching or exceeding limits?
We’d like to query Jira for issues that are nearing or have surpassed limits on specific parameters to proactively manage them.
Are there limits on issue history?
Will the issue history be restricted to a certain number of entries?
Internal issues used company-wide often surpass limits faster.
Time is frequently logged to internal issues in Tempo, which are used across the company and can exceed limits more quickly than other issues. What steps can we take to manage this?
It will be great help to get answers as per latest updates to my queries.
"Linked issues are limited to 2000 per issue. This does not include child issues."
What does it mean that this limit does not include child issues? I have a parent issue currently that has more than 2000 child issues and is throwing an error "ISSUE_LINKS_PER_ISSUE_LIMIT_EXCEEDED: 2000"
It would seem that child issues are not exempt. Or am I misunderstanding the limit?
Well great^^ at our company, every employee has to log their breaks, because it is required by law in our country, to log breaks. So now, every employee is frustrated, because jira doesn't have a built-in "break" task, which could be ignored. So we use a task for that, so that HR and all those who are involved in monitoring an employee's work-log and break, know exactly which task to subtract from the total working hours.
It would have been nice to have an option to exempt a worklog from this rule for such corner cases.
But yeah. I guess ours is not the only company where people are frustrated with this change.
We have prepped for this change and asked for guidance from Jira and tempo for a real solution for months and we were still blindsided, each team has time split out, and we now export time out every month, but we must still keep a minimum of 90 days of time. The amount of edge cases that have shown up are crazy and we are still desperately needing a better solution to this instead of what Atlassian has come out with, which is almost nothing.
I found that what API gave me as the number of worklogs per issue is different to the one on the UI. Is there a delay of this number to reflect on the UI after worklogs being moved via API?
Users are unable to log time with error:
Error!
Can't add a new worklog because Jira's worklogs per issue limit has been exceeded
:( This has just bitten us - after clearing/moving worklogs a few months back, all our employees can no longer log internal work as we've exceeded the 10k limit far quicker than expected.
We're trying to bulk move worklogs to get us back up and running as quickly as possible using Tempo's bulk editor, but it seems to be hanging after 10 minutes of not showing any progress. Whilst Jira or Tempo thinks it's "running," we can't move any other worklogs via the UI, so our company's time recording solution is effectively down.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Given that Altassian's Forge framework uses a partial implementation of the node-fetch module to underpin the requestJira() method to access Jira's REST API, and that node-fetch doesn't support passing parameters in the body of GET requests, how will developers using Forge build applications to access the new Get issue limit report endpoint?
@Apoorv Aggarwal that's great, but it's still not enough. For certain things which must be logged in a uniform way (due to laws in certain countries) any limit set will not be enough. If every employee in a company has to log their breaks every day, a limit of 10k, 50k, 100k will simply be exceeded rapidly based on the size of the company. The same goes for vacations, official meetings or company events and basic administrative tasks, which are not really part of a project, but must be logged as a work activity, because that is what the law states. So now every company must dance around this restriction while still remaining efficient within their company's organizational structures and also logging in accordance with the law.
So perhaps if there were a time log type that is not associated with a project per se, but could still be taken into account in the overall work log, that would be a more sensible solution than treating every log as part of a project, including all of the additional functionality. I am sure this would be possible to do efficiently for a company of your size with your means^^ There are no due dates, deadlines or dependencies for something like a break. But breaks must be logged according to the law in Germany... and very likely in all EU member states.
96 comments