Is it possible to transform data in Jira DC and export to Excel?

[Rita Arellano]

Hey All, 

We have a field limitation in our organization and have needed to think of creative ways to mitigate these limitations. We capture all 25 of our teams hrs. per ticket and we do so through a text field. As you can imagine this field is a nightmare when exporting to Excel as its very long. So our text field looks something like this:

Field: Hrs. per Team

Values: team a : 24
            team b:   9
            team c:    0

Is it possible through any means to get to a way in where one can parse out the team's names - convert to columns and the hrs. which come after the delimiter turn into values of the team's ? I would like to export this to Excel and use Jira automation maybe some JSON. I have Jira Data Center. Maybe I'm just mad now, but is something like this even possible?

Desired Outcome

team a         team b          team c
   24                  9                   0

[John Funk]

Hi Rita,

So why are these not separate fields in Jira? 

[Rita Arellano]

Hi @John Funk 

We have field limitations and I was told by ITSM in my organization that adding 25 fields dedicated to our teams would slow down the Jira instance for all users. 

[John Funk]

Yes, you want to control the over proliferation of fields in Jira but you can mitigate that with adding contexts to the fields. Also, I see 3 fields, not 25. And causing WAY more work to compensate for not having the fields doesn't seem like good business practice either to me. 

[Rita Arellano]

I did not want to type all 25 fields. I just provided 3 fields to provide a big picture of what I wanted to achieve. I agree this seems like a lot of work. Curios, how do you add context to a field?

[John Funk]

Go to Settings > Issues > Custom Fields

Search for your field and then click the 3 dots to the far right. Select Configure Contexts

There you can edit the Configuration to make the field relevant to only certain projects and/or issue types. This is what keeps the fields from being a burden on performance. You should not have a bunch of custom fields that have just a Global Configuration.