Does Configuration Manager for JIRA plugin support for post function and custom fields?

Question

we are using JIRA 6.4 and JiraServicDesk 2.5.9 in Test environment.

we have created a JiraServiceDesk project(Test_Application)

----------------

(Test_Application) project have

1) Custom fields(database field ,script fields)

2) Issue Types,Issue Type schemes

3) Workflows and workflows schemes

4)Field configurations and Field configuration  schemes

5) Post functions ,conditions and validators

6) Filters

7) Automation Transition Rules

8) SLAs

9) Queues

10) Request Types

11) Email setting

We are planning to use Configuration Manager for JIRA addon/plugin to try and refresh our Production environment from Test environment JIRA.

Our challenge is to be able to copy only the Configuration items over from Production into Test.

Is it possible to Replicate the configuration from Test environment to Production environments,without doing additional changes?

Please suggest us to follow the steps to take snapshot and copy to Production environment...

George Dinkov _Botron_ · Answer

Hi Guhan,

Since version 4.0 (available since April) CMJ supports Agile boards. For more information you can review the docs here - https://botronsoft.atlassian.net/wiki/display/CMJ/Agile+Boards

Thanks!

unknown · Answer

George, may I know when we should be able to migrate the Boards successfully using Configuration Manager? We are in the latest version of JIRA Server and purchased CM too.

George Dinkov _Botron_ · Answer

Hi Sindhu,

Configuration Manager for JIRA supports all native configuration objects in JIRA - this includes custom fields, issue types, workflows, post functions, field configurations, all schemes, filters, etc. and a lot more are coming in future releases. For more information you can check this page - https://botronsoft.atlassian.net/wiki/display/CMJ/Configuration+Object+Support+Matrix

Unfortunately CMJ currently doesn't support Service Desk specific configuration (SLAs. queues, etc.). This is on our roadmap for future releases.

With CMJ it's fairly straight forward to setup such process - just create a snapshot on one server, download it (or link the servers with Application Links) and deploy it to the other - this will give you a detailed overview of all the differences and what is going to be merged, also every single change is audit logged for later review/auditing.

Thanks,

George