Multiple Epics with Differing Customized Fields within the Same Project?

[Jamie Roth]

Hi I am wondering if it possible to create multiple epics within the same JIRA Project that have a unique set of customized fields on each issue within the respective epics. In other words, can Epic A have issues with fields 123 while Epic B has the same issue types with fields 456? 

[Chris Buzon · Accepted solution]

No, If they're within the same project then you cannot have different fields if it's the same issue type. 

Basically, you control what fields are visible through a combination of field configurations and screens / screen schemes, but there isn't any (that I know of) way to further subdivide at the issue-type level.

[Jamie Roth]

Cool thank you. I had someone asking for individual Epic customization and I really really wanted to try for her, but I didn't think it was possible. Knowing I have now exhausted all options, I can feel better when I tell her that we will have to try something else. Thank you kindly! 

[Andreas Haaken (APTIS)]

Hi @Jamie Roth , 
may I ask what the use case is for the different fields? 
Do you want to show values somewhere?

[Jamie Roth]

Hey @Andreas Haaken (APTIS) Thank you for the reply. Essentially I had a request come in for a  new Project space. The person who requested doesn't seem to know a lot about JIRA, and to be fair, I am always learning. I am the company's JIRA Admin by default, lol. I 

Anyway, she is trying to create division for different types of bug and task tickets related to our company's various platforms. A particular group of bug tickets she wants tied to one epic (lets call that Epic A). These are all related to different reports that can be run so when something needs to change or there is a bug with the reports, she would like a drop down to indicate which report is in question. To address this, she has requested that I add a customized field and that the particular field be mandatory... so far so good. I can accomplish all of those things...

But she also asked to have another epic (lets call that Epic B) that has a different drop down with entirely different selections for the bug and task tickets created there which will address issues found on our production servers for our platforms.  The fields are not applicable to both types of tickets in each Epic. In other words, it does not make sense to have Field 1 on Epic B. And it would not make sense to have Field 2 on Epic A. They must be A1 and B2 respectively or else the process she wants to design will fail. 

I was looking for a way to accommodate her request, but apart from adding a NA value to each drop down and requiring both fields then I do not see a way to differentiate these issues for her. I have also suggested creating a label, but she is not keen on anyone having to type in their label... I think she is primarily worried about compliance. Anyway, I would appreciate any help you can give. Thank you so much for reaching out.

[Andreas Haaken (APTIS)]

Hi @Jamie Roth , 

Ok, so lets go into it, I have some more questions:

• what kind of reports do you use? Or want to use?
• the Epics are working as a folder of tickets right? so what is the meaning of having different epics? (the values in the dropdown could be a merged list of all values so you don´t have to use 2 different field)
• Use of that solution: What do you want to achieve basically? (related to the report you mentioned?)

If you have a screenshot displaying your scene would be great.