Project Keys

[Beth Pettit]

Can a single Jira project have numerous keys? 

I'd like to organize my Program, which is comprised of many lines of effort, using built in Initiative, Epic, Task hierarchy. Ideally, I would like to assign a different key to the issue type rather than the project to differentiate between work. (We are currently hard-coding change of naming convention on issue types, i.e. New Feature --> custom name 

We are managing customer facing requests in Jira Service Desk and we are standing-up a hierarchy to manage components of the program. I want to differentiate between these two without have numerous projects in Jira. How do I do this? 

[Nic Brough -Adaptavist- · Accepted solution]

I suspect you'll find all the struck-out issues have had their "resolution" field set to "something other than <null>"

You'll need to run some simple searches to test that assumption, and if I'm right, you'll need to do one or two things eto stop it getting wors - remove the resolution field from where-ever you've added it and/or remove corrupting resolution values from the list. Then you can clean out your data.

I'll explain that more if you need it later, please test for it before I start rambling!

[Gavin Beddow]

Hi Nic,

Thanks for your prompt response. I've done some checking and it looks like we had an 'unresolved' item in the resolution field that was getting applied by default when the ticket was updated.

Removing that seems to have resolved the problem.

THanks,

Gavin