advice on DEV-QA-PROD environments...?

[llagos]

Hi Community!

We are new to Jira, and we (the customer) want to have 3 separate environments for dev, qa, and prod.

However, our Jira partner implementing here has told us that it's not possible to export a configuration (flow) from one server to another; but instead, we need to have all in one server, but in different projects, and so we can use a "export flow" functionality.

However, this is not acceptable to our internal IT team.

In fact, we've doing changes in another project "devsd" and doing the exporting, but some changes need a total restart of Jira, while others are system-wide, and not just project-speecific.

So, I wonder and ask, if this so? If not, how do You manage your dev, qa, prod, environments?

Thanks a lot,

[Tom Lister · Accepted solution]

Hi @llagos

I have always used a dev , qa & prod setup. Although it's not without its challenges. And their approach may be easier.

For a new piece of work each group, permission, workflow and script has to be set up in each instance. Workflows can be exported and imported but only if the environments match exactly.

Our approach was to 

- make a detailed map of what we intended to implement

- make changes in prod that would not affect functionality e.g. create project, groups, roles, schemes but not make them visible to current users

- export to dev or qa for system or user testing.

- make any changes in prod and go round cycle again

Its quite laborious. I worked for a bank with very strict processes for how changes could be made in production and this was the compromise we came to.

Check the market place for tools like Project Configurator that may help