Help! I changed the workflow for multiple projects instead of just the one I wanted

[Tzirel Shaffren]

We have multiple projects that share a single workflow. I will call the workflow "SharedWF". I created a Sandbox Project and used that shared workflow.

I wanted to change the workflow on the sandbox project. Somehow I managed to change the workflow on all the projects that used the Shared WF.

This is what I did:

1. I made a copy of SharedWF, and made all kinds of changes to transitions. (I believe I saved, or Published)
2. I went to Gear > Issues > Screens > copied the Shared  Screen
3. I went to Gear > Issues > Screens Scheme and copied the Screen Scheme
4. I went to Gear > Issues > Issue Type Screen Scheme > Add > Clicked on 

   Associate an issue operation with a screen and chose my copied screen

5. I went to Gear > Projects > 3 dots next to my project > Project Settings > Workflow Schemes > Edit > Add Workflow > Add Existing > and then selected my new Workflow (for all the issue types)
6. Publish > Associate

I obviously did something wrong because all the projects that shared that Workflow now have my new workflow.

I even took a screenshot that shows that the Screen Scheme was associated with the sandbox project. I can't figure out how to attach the screenshot to my question.

Can anyone help? 

[Nic Brough -Adaptavist- · Accepted solution]

There is something wrong with the settings on your SQL server.  A simple indexing from Jira might cause high load (as it reads every single issue in the database as fast as it can), but it won't crash it.  It's not doing anything other than reading.  If your database can't cope, it's a problem with the database.

[Walid Djama]

So if i understand correctly, if the consumption does not go down after the indexation it's a database problem ? 

[Nic Brough -Adaptavist-]

Possibly.  Have a look at the queries being run - I would expect to see indexing running many sequential reads while running, and then revert to relatively low usage afterwards, writing issue and settings updates as users use Jira and reading when issue views or certain types of query happen (the index and caches are used for most reporting, to keep the level of database access low)