Challenges of Archiving of a jira project with our approach

[jira-qa-useradmin_mobily_com_sa]

We are exploring archiving options and decided to archive in the following way :

1. We have created a new project and will ask users to create ALL new issues in the NEW PROJECT named 'Welcome2019' .

2. We will continue using existing project 'Welcome2018' ONLY for the existing issues however using project permissions, won't let them create any new issue in this project.

And eventually, archive this project when all its issues reaches to done state.

3. For the project 'Welcome2018', Challenge we are facing is because we have denied users from creating new issues using "create issues" project permissions, it wont auto-create subtask/child issue types as scripted in the workflow for the existing issue items.

I mean to say if I have a issue type 'Release' and it has a subtask issue type 'Deployment' at certain state in the workflow.

Because of 'Create Issue' project permission blocker we enabled, existing release items won't have deployment subtask auto-created as it would if this permission was not denied.

Appreciate if anyone suggest any suggestions or a workaround to fix this challenge.

[Tarun Sapra]

Hello @jira-qa-useradmin_mobily_com_sa

Jira project permission are not available per issueTypes, thus if you have a paid plugin installed like Script Runner or Automation then you can add a condition in the "Validation" phase of the create transition to block creation of the all issueTYpes which are not "sub-tasks" with an error message "Project Archived, new issue creation not allowed"