Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

ScriptRunner: Config exporter vs. configuration exporter

Can anyone tell me what the difference is between Config exporter and Configuration exporter in ScriptRunner?  I see both options in the System category when browsing the built-ins.  We haven't been using it for long and I'm curious what the former (Config exporter) does.  I've tried looking through the docs and can only find information about the latter (Configuration exporter).

I've tested to see what Config exporter does--all you have to do is choose a directory to save the export.  I've done that, and I see it builds a file named "CurrentConfig.groovy", as well as a sub-directory "workflows" which contains one XML file for each workflow in the exported instance.  The .groovy script begins with

package com.onresolve.jira.upgrades

import com.atlassian.jira.component.ComponentAccessor
import com.onresolve.jira.groovy.metadata.JiraMetadataDSL
import groovy.transform.BaseScript
import com.onresolve.jira.groovy.metadata.workflows.WorkflowsMigrator
import com.atlassian.jira.issue.operation.IssueOperations

@BaseScript JiraMetadataDSL dsl

def i18nHelper = ComponentAccessor.getJiraAuthenticationContext().getI18nHelper()

ComponentAccessor.getJiraAuthenticationContext().setLoggedInUser(ComponentAccessor.getUserUtil().getUserByKey("admin"))

and then basically contains objects for all of the following from the instance:

  • Issue types
  • Issue type schemes
  • Screens
  • Custom fields
  • Screen schemes,
  • Issue type screen schemes
  • Statuses
  • Workflow schemes
  • Permission schemes

Not being sure what it was meant for, I did an export from our prod instance, copied the exported files to the dev box, then tried to use the ScriptRunner console to run that CurrentConfig.groovy file, but it throws some errors (not surprising).

Can anyone tell me what the use case for the Config exporter is and how to use it properly?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

76 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you