Emre Toptancı [OBSS] Atlassian Partner

Hello @Parker Lovelace I suggest you take a look at the original Timepiece - Time in Status for Jira by OBSS. Our app does exactly what you need * Our app creates reports on how much time each issue spent on each status, assignee or user group. * Number of time each status or transition was used. * View durations in days,…

Hello @John Monczewski I suggest you take a look at the original Timepiece - Time in Status for Jira by OBSS. Our app does exactly what you need * Our app creates reports on how much time each issue spent on each status, assignee or user group. * Number of time each status or transition was used. * View durations in days,…

Hello @Anne-Laure Caluori I suggest you take a look at the original Timepiece - Time in Status for Jira by OBSS. Our app does exactly what you need. * Our app creates reports on how much time each issue spent on each status, assignee or user group. * Number of time each status or transition was used. * View durations in…

I suggest you take a look at the original Timepiece - Time in Status for Jira by OBSS. Our app does exactly what you need. We now have Server, Data Center and Cloud support. The app Mark mentions is sadly a copycat of our product.

Those post-functions for reindex were always present by default in every transition but they reindex the individual issue. The reindex Dmitry is looking for reindexes the whole Jira system.

I implemented the SearchProvider approach and got very good results. It is poorly documented (as usual) so requires some trial and error but sure works. Using this approach I made a search that only returns issueIDs (List<String>) which uses very little memory. Iterating through this list I retrieved each issue…

Thanks Anton, I didn't try that and it sure looks promising. While searching for a solution, I actually came across some other answers pointing to this but the answers mostly emphasized this was moved out of the API and the best way to go was to use SearchService. So I saw it as a deprecated api. Anyway, I will try to…

I found some classes like CalendarService and WorkingHoursCalculatorService in "com.atlassian.jira.plugins.workinghours.api" package. and TimeMetricService in "com.atlassian.servicedesk.api.sla.metrics" package. Did my thing with those.

With a little bir of tweaking I got it to work. I can successfully dispatch an event and catch it in the other end. HashMap<String, JsonNode> params = new HashMap<>(); params.put("myKey", new TextNode("myValue")); Issue updatedIssue = issueManager.updateIssue(updater, targetIssue, UpdateIssueRequest.builder()…

The question I asked explains the requirement in an oversimplified fashion. To give a little more detail I can say that Issue A will update not only Issue B but potentially update a number of issues and each issue might respond with the update of a number of other issues as well. The event mechanism is the perfect fit for…

Hi Micky, Thank you for the direction. The document you sent has instructions for 2.x+ version of Spring Scanner. It turns out my plugin uses the older version so I have several <component-import> statements in my atlassian-plugin.xml file. I added the interface I need into atlassian-plugin.xml, like ... <component-import…

Hi Micky, Thank you. Looks promising but I couldn't get it to work. RequestTypeQuery and RequestTypeQuery.Builder are interfaces and mighty Atlassian documentation does not give information about classes who implement this interface. I browsed through the IDE and found a class named RequestTypeQueryImpl. This class is an…

Totally my bad getEstimate() already returns values EXCLUDING subtasks.

Thank you for the answer. I asked our BitBucket admin to see if these plugins are installed. Waiting for the answer. On the other hand I am still not sure why this happens. I have been using BitBucket for months and never faced this issue before. Same server, same user, same user PC. It is only me that works on my PC so I…

Hi Branden, We also have a few customers with close to a million issues and with careful configuration they are working relatively fine. The sizing guide you mentioned (or any other JIRA performance optimization resource) only focuses on number of projects, custom fields, issues, schemes, etc. Since exam prep material…

Hi Ann, In fact our situation is a little bit different than you described. JIRA is connected to Crowd and Crowd is connected to LDAP. We did not deactivate the user on Crowd, the user was removed from LDAP and both JIRA and Crowd were moved to a new server via XML backup. After moving to a new server, JIRA can see the…

I'll see what I can do. Thanks...

Actually our current situation is deeper than that. Customer has a system with around 1000 custom fields. Many of these fields are kept just to use the hold information on the form, they are not used for JQL searches. On one side I am pushing the customer to consolidate and reduce the number of fields, on the other side I…

What we do for performance improvement on large systems is to limit contexts of custom fields to specific projects and/or issuetypes. This proved to be useful since it reduces the information to be indexed significantly. I see "setting the searcher to None" technique as a next step to this approach. Let's say we are…

We hit the same problem and could not restart JIRA (business limitations) It turns out the mail queue has crashed. Changing interval of mail queue service to some other value forced it to to restart and it started working right away without a complete JIRA restart

I am in the same situation with JIRA 6.3. The problem is, some of the users that are expected to open tickets via e-mail are also users of other projects in my JIRA system, so I can not deny them login. I also can not grant them create issue permission on my project because there are other issue types in the project and…

Yes, that is more promising if used in conjunction with created date. Something like: created > -2d and "Time to resolution" < remaining ("-1d") Issues that were opened in the last two days and "Time To Resolution" was breached less that a day ago. Still not exactly what I am asking for but seems to do the trick.

Hi, Yes this can filter out most of the issues but it is based on creation date, not SLA completion date. I gave an example in the question with one SLA for the sake of simplicity and this works with one SLA definition but it fails if I try to do the filter with two SLA definitions with different SLA target durations. On…