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? 

[Kepio · Accepted solution]

I figured out the approach by browsing the source code of https://studio.plugins.atlassian.com/svn/JDVP/tags/database-values-plugin-1.3/

The atlassian-plugin.xml definition pretty much gives the answer :

<webwork1 key="multiple-cascading-select-cf-type-configuration" name="Multiple Options Cascading Select Field Configuration">
		<description>Configuration for the Multiple Options Cascading Select Field Field.</description>
		<actions>
		    <action name="com.company.plugins.jira.customfields.config.EditMultiCascadingCustomFieldOptions" alias="EditMultiCascadingCustomFieldOptions" roles-required="admin">
        		<view name="input">/secure/admin/views/customfields/editcustomfieldoptions.jsp</view>
        		<view name="error">/secure/admin/views/customfields/editcustomfieldoptions.jsp</view>
        		<view name="confirmdelete">/secure/admin/views/customfields/deletecustomfieldoption.jsp</view>
        		<view name="edit">/secure/admin/views/customfields/editcustomfieldoptions.jsp</view>

        		<command name="configureOption" alias="ConfigureCustomFieldOptions">
            		<view name="error">/secure/admin/views/customfields/editcustomfieldoptions.jsp</view>
        		</command>
    		</action>
		</actions>
	</webwork1>

From there- you can:

• modify the jsp file EditMultiCascadingCustomFieldOptions extends EditCustomFieldOptions and overwrite my public function
• modify the templates directly if need be - in my case, I re-used the native ones