I’m trying to find out how to rename a JIRA project that I already have set up. It’s important to note that I’m not looking to change the project key, as I’m aware that’s a fixed element. My current setup is on JIRA Cloud, and this project has various issues that are still open and have been resolved. Since the project has been in use for some time, it has accumulated a number of tickets across different stages. Can anyone help me with the process of just changing the project name? I’ve checked the settings but can’t seem to locate the option. Any assistance would be much appreciated, as this update is needed for my team’s workflow.
definitely back up your dashboards and filters! renaming can mess with saved searches. it’s pretty simple in project settings but keep an eye on third-party apps. they might still show the old name for a bit.
Go to your project and click the gear icon (bottom left). Then hit Project Settings > Details. You can edit the project name if you’ve got admin rights. I did this last year when our department restructured - had to rename several projects. Pretty straightforward, but I’d do it during off-peak hours. JIRA handles the backend stuff fine, though some users got confused with search results right after. The change goes through in minutes, but browsers might show the old name briefly due to caching. Make sure you tell stakeholders who use the project in reports or dashboards - some external docs will need manual updates.
To rename your JIRA project, click on the gear icon in the lower left corner to access Project Settings. Select ‘Details’ from the sidebar menu. If you have the necessary admin permissions, you can directly edit the project name at the top of the page and save your changes. Rest assured, the new project name will reflect on all existing and future tickets. It’s wise to inform your team to prevent any confusion during their searches.
The manual approach works, but here’s something different for the long term.
If you’re renaming projects regularly (team restructures, client changes, etc), you’re probably wasting time on other JIRA admin tasks too. I used to spend hours monthly on project maintenance.
Now I handle everything through Latenode automation. Set up workflows that rename multiple projects at once, sync names with external systems, or auto-update based on triggers.
Last quarter we had a major reorg. Instead of manually updating 20+ project names one by one, I built a flow that pulled our new naming convention and updated everything in bulk. Saved me a full day.
You can automate communication too - send Slack notifications to affected teams when names change, or update Confluence pages automatically.
For now, just use the project settings approach others mentioned. But if this becomes regular, automation beats manual every time.
just head to the proj settings in the side menu, look for ‘proj details’ and you should see the name field ready to edit if you have admin rights. no worries, all your current tickets will still be linked once you change it.
Check your permissions first - this catches tons of people. You might have admin access but not project admin rights (they’re separate). Go to project settings in the sidebar, find Details, and the name field should be editable there. Heads up: tell your team before you change it. They’ve probably got bookmarks and saved filters with the old name. JIRA updates everything on the backend automatically, but people get lost searching for the project later. One more thing - the project key stays the same like you said, but some integrations or external tools pull the project name directly. You’ll need to update those manually after the rename.
You need admin permissions. Go to Project Settings > Details - the project name field’s right there.
If you’re doing this admin stuff regularly, you’re probably stuck with other repetitive JIRA tasks too. Been there.
I automated most of my JIRA management through Latenode. Set up workflows for bulk project updates, auto-rename projects based on criteria, or sync project names with external systems.
Last month I had to update 15 project names across different JIRA instances for a reorg. Instead of clicking through each one, I built a simple automation that pulled new names from a spreadsheet and updated everything in minutes.
Manual way works fine for one project, but automation saves tons of time if this becomes regular.