nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ScriptRunner: Iterating through an issue filter to calculate number of issue created by person

Alexey Paveliev_pgpak4

I was asked to provide stats for all users submitted issue in the last year.

My first thought was export issues to Excel which seemed to disappear.

So I created a script to run in the console to do the math which worked but only up to 100 maxResult

def query = 'project = "Project name" AND created > "-365d" ORDER BY created ASC'

def searchReq = get("/rest/api/2/search")
.queryString("jql", query)
.queryString("maxResults", "1000") //only returns 100!
.asObject(Map)

Map searchResult = searchReq.body

def issuesByUser = [:]
def user = ''
def count = 0
searchResult.issues.each { Map issue ->
user = issue.fields.reporter.displayName
created = issue.fields.created
count += 1
//logger.info("${count} ${user} ${created}")
issuesByUser.putIfAbsent(user, 0)
issuesByUser.find{it.key == user}.value += 1

}
logger.info("Total ${count} issue")

def total = 0
issuesByUser.each {i ->
logger.info("${i.key} ${i.value}")
total += i.value
}
logger.info("Total ${total} issue")

I could use some help with that!

Thank you

Accepted answers

Kristian Walker

Hi Alexy,

When using the Search for issues API if you want to return more than 100 issues you will need to use pagination by having multiple search queries which the extra issues.

This means for the second query and onwards you would an extra queryString paramater of startAt as documented in the API documentation page above as this would return the next 100 issues if you started from 100 and then 200 etc.

I hope this helps.

Regards,

Kristian

All comments

Hana Kučerová

Hi @Alexey Paveliev ,

I will try to help you with the code, but please, did you try Pie chart gadget? It should give you the same results without groovy scripting...

Hana Kučerová

Oh, I mostly forget on Issue statistics gadget - it can be used, when you want only simple table :-)

Kristian Walker

Hi Alexy,

When using the Search for issues API if you want to return more than 100 issues you will need to use pagination by having multiple search queries which the extra issues.

I hope this helps.

Regards,

Kristian

Alexey Paveliev_pgpak4

Thanks!

there are around 1200 issues submitted by too many people to fit in a chart

Alexey Paveliev_pgpak4

Thanks.

Just did that and got "Execution timed out after 60s."

Alexey Paveliev_pgpak4

def query = 'project = "Project name" AND created > "-365d" ORDER BY created ASC'

def issuesByUser = [:]
def user = ''
def count = 0
def pageSize = 100
def issuesGot = 0
Map searchResult = [:]
def totalIssues = 0

while (true) {
def searchReq = get("/rest/api/2/search")
.queryString("jql", query)
.queryString("maxResults", issuesGot+pageSize <= totalIssues ? pageSize : totalIssues - issuesGot - 1)
.queryString("startAt", issuesGot+1 )
// .queryString("fields", "Flagged")
.asObject(Map)
issuesGot += pageSize

totalIssues = searchReq.body.total
logger.info("Total issues ${totalIssues}")
//logger.info(searchReq.inspect())

searchResult = searchReq.body

searchResult.issues.each { Map issue ->
//print (issue.fields.reporter.displayName)
user = issue.fields.reporter.displayName
created = issue.fields.created
count += 1
//logger.info("${count} ${user} ${created}")
issuesByUser.putIfAbsent(user, 0)
issuesByUser.find{it.key == user}.value += 1

}
logger.info("Total ${count} issue")
if (count >= totalIssues) break
}
def total = 0
issuesByUser.each {i ->
logger.info("${i.key} ${i.value}")
total += i.value
}
logger.info("Total ${total} issue")

Alexey Paveliev_pgpak4

See code below that times out at issues over 1200 but luckily works up to 1000 issues

Kristian Walker

Hi Alexy,

I can confirm that we impose a timeout limit on scripts of 60 seconds in order to prevent long-running code as described in the documentation page here.

This means you will need to split your logic up into multiple scripts if your script is exceeding the 60-second timeout limit.

However, I notice from your script you have the line of // .queryString("fields", "Flagged") commented out which means as you are not restricting the fields you need on each issue that you are returning every field on the issue which would cause the search API to take a long time to return.

I would advise uncommenting this line and only returning the fields you need on each issue and if you are just counting the issues then just to return the summary field as doing this will cause the API to return faster and may help with the timeout limits that you are getting.

Regards,

Kristian

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira

cloud

jira-software

jira-software-cloud

adaptavist

groovy