Gabrielle is doing exactly what the standard approach is. There's no "close project" function, as it's something you need to define for yourself really. So, you need to decide what your users can do in a "closed" project, build a permission scheme for it and apply it to your "closed" projects. Your main decision is probably "who can browse closed projects"
You simply can't "close" a project in JIRA.
if you delete a project it's deleted. You can't close a project in the classic project meaning.
When you want a project with start and end date you should use the versions of a project or configure issue types with name project.
Projects would be in this case like departments or products.
and you issue types could be projects, mile stones, task, sub-task to break down your issue-like project.
Project ~ DEV
Issue types = Project - is blocked by Issue types = Mile stones - is related to Issue types Task which have subtasks for a assignee based breakdown.
Basically, if you`d like to follow with Gabrielle's solution, I believe these 2 pages will be able to guide you:
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs