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; } } }

Groovy Post Function -- best way to get all populated fields (system and custom) for an issue?

Bryan Karsh

I'm looking for the best way to grab all populated fields for an issue (both system and custom) in a groovy post-function (which will then be passed on to some other scripts for some automated tasks). Below is a way I was able to do it, but I fear that I am using non-standard or deprecated means to go about it. Can someone take a look, and let me know if it looks good?

import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.issue.Issue

IssueManager issueManager = ComponentManager.getInstance().getIssueManager()
CustomFieldManager customFieldManager = ComponentManager.getInstance().getCustomFieldManager()


myissue = issue.key

Issue issue = issueManager.getIssueObject( "$myissue" )

def cflist = customFieldManager.getCustomFieldObjects(issue)

def map = new HashMap&lt;String,String&gt;()

cflist.each {cf -&gt;
Object value = issue.getCustomFieldValue(cf)
if(value){
    map &lt;&lt; [(cf):"$value"]
}
}

def systemfields = issueManager.getIssue("$issue")  //using GenericObject since it seems to contain issue fields -- appreciate alternative suggestions

def iterator = systemfields.entrySet().iterator()

while (iterator.hasNext()) {

  if (! iterator.next().value) {
    iterator.remove()
  }
}


map &lt;&lt; systemfields

def body = map.collect { k, v -&gt; "${k}^^${v}" }.join('::')

Accepted answers

JamieA

I'd say why do you want to do this?

Having said that, what you're doing doesn't seem too outlandish. You don't have to use the GenericValue but then you do need to list out all the fields, and then maybe use the issue.@property notation, if you want to iterate over a list of issue fields.

All comments

Bryan Karsh

Let me also say that Groovy is not a langauge I am very good at -- so apologies for syntactical weirdness.

JamieA

I'd say why do you want to do this?

Bryan Karsh

Well, several teams use Jira at our company. One request is that we have some mecanism in place that will pass populated fields from issues in a particular format, that can be parsed by scripts, etc.

One use case we had recently, was a customer wanted to be able to resubmit a transaction -- the ticket took the transaction -- passed the info to a script on the backend that reprocessed the transaction, and then the output from the transaction would be commented in the ticket. Basically we'd be using Jira tickets as a front-end interface for some of our tools.

The reason I am grabbing all fields is that I don't want to customize the code for this type of project vs. that type of project -- it should just grab everything (except comments), and our devs could mince/use the data as they see fit.

JamieA

OK... but the map you are creating is not very good for an interchange format. You should use something easy to parse... jira can create both JSON and XML representations of an issue, including all comments, history etc, not just fields.

You should reuse that... then you can just stick your bit of JSON on the message bus or whatever it is.

JamieA

Also note that this is pretty much what WebHooks are for - and all that code is already written.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

custom-field

post-function

field