It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to hide 'Epic Link' field via Field Configuration?

Normally, visibility of fields in JIRA is configured with Field Configurations and Screens. The field needs to be configured for the issue type and for the screen to become visible.

I have different issue types in my project and they have different field configurations, each selecting a subset of applicable fields. The screen configurations (e.g. create issue screen) are not issue type dependent and include all fields.

This works well with pretty much all fields, so only those applicable to the issue type are shown.

However, 'Epic Link' can apparently not be configured this way and I am puzzled about the restriction. I want to use Epic Link for some issue types, but not for all. How can I hide it without duplicating all my screens?

2 answers

1 vote

Because Epic Link is a System Field, not a Custom Field, it cannot be configured per issue type using either Field Configuration or Field Contexts. This is the same with configuration of other System Fields such as Priority and Resolution. 

In other words, with Jira Software installed, all non-subtask issue types will have the ability to set the Epic the issue is linked to. The only way to suppress this for a given Issue Type is by not including it in the Create/Edit/Other screens for that issue type.

The Epic Link field is Locked:

epic-field-locked.png

The Epic Link field does not have a "Configure" option. It only has links to change the Screens that it appears in:

epic-field-configure.png

Cheers,
Morgan

@Morgan Knicely: thanks for the response. I understand why the field cannot be hidden as it is a system field and therefore treated special. The problem may therefore not be an 'implementation bug', but a design issue. Why should the software prohibit hiding the Epic link field through field configurations? 

As stated in the original post: 

I have different issue types in my project and they have different field configurations, each selecting a subset of applicable fields. The screen configurations (e.g. create issue screen) are not issue type dependent and include all fields, e.g. I have a single create field screen at the moment.

This works well with pretty much all fields, so only those applicable to the issue type are shown.

However, 'Epic Link' can apparently not be configured this way and the restriction feels entirely unnecessary. I want to use Epic Link for some issue types, but not for all. How can I hide it without duplicating all my screens?

Just one example: showing the epic link field for epic issues while showing a message that it is not applicable in this context is bad UI style. 

Create Epic Issue.png

Can you elaborate why it needs to be this way, rather than why it technically is this way?

As a consequence, I would need to duplicate my create issue screen ... and my edit issue screen... and a number of workflow screens, just to have one version with and one without the Epic link field. Feels wrong.

A year later, but while M.S. should be creating screens for the create and edit actions for each issue type--I still wish we could configure the Epic Link in the field schemes.

My use case is a special project within our Jira that is used as a "trash" project--it's literally called that. Rather than allow deletion of issues, all users can move issues into TRASH but nobody but system admins can see them. Moving something to TRASH is, effectively, the same as deleting it for the end user. This is so issue "deletions" can be reversed if necessary.

However, this can cause a problem when issues have an epic link when they are moved to the TRASH project. Our workflow checks require all child issues of an Epic to be done before the epic itself is finished; it would be nice to hide the Epic Link field in this project so the value is automatically stripped on move.

0 votes
Scott Theus Community Leader Apr 24, 2018

I've wracked my brain over this and the short answer is that I don't think you can without at least setting up a screen scheme for the "Epic" issue type. From there, add a custom check box for "Show Epic Link" and some conditions on the Epic Link field to only be visible when that box is checked.  

 

-Scott

Not sure I understand that response. Why would I need a checkbox? Perhaps my question was misleading. I want the Epic Link field to be shown for some issue types, but not for others. I do not need to differentiate between issues of the same type.

It puzzles me that I can do this with all other JIRA standard fields (well, except what is obviously mandatory) as well as any custom field, but not with Epic Link. I do not see a reason why Epic Link would need to be so special.

How can this be raised to Atlassian's attention?

Scott Theus Community Leader Apr 27, 2018

Ahhh...I understand. I tested it and ran into the same problem. I created a new issue type screen without Epic Link and a screen scheme that included it, using Create, Edit and View for that type with the new screen. The Epic Link field remained available in each function. 

I suggest raising it as an issue by clicking the create button and reporting it here:

https://jira.atlassian.com/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all

If you don't mind, post a link to the new issue in this thread, I'd like to watch it.

 

-Scott

I would, but that page does not let me create a new bug report. Instead it leads back to the forums. 

How do I raise a bug/support request (I am on a 10 ppl starter license)?

@Ann Worley is that something you can look into?

 

I should add that it seems that you went through screen schemes, whereas I tried it through issue field configurations. Neither seemed to work.

Ann Worley Atlassian Team Apr 27, 2018

@M.S. When you go to our support portal (https://support.atlassian.com/contact) and enter your Support Entitlement Number for a starter license you will be directed back to the Community forum.

I just tested our issue tracker (at https://jira.atlassian.com) and was able to create a ticket as an end-user (not my Atlassian employee account). If that site is also directing you here, please post a screen shot of what the deflection page looks like. Please include the URL from the browser in the screen shot.

So on jira.atlassian.com I can click Create: 

2018-04-27 23_23_48-Create Issue - Create and track feature requests for Atlassian products..pngWhen I click on the blue report a new bug, it leads me to https://support.atlassian.com/jiracore/

When I enter information instead, and click Create I get this:

2018-04-27 23_27_04-Create Issue - Create and track feature requests for Atlassian products..png

Ann Worley Atlassian Team Apr 27, 2018

I just tested further and got the same result you are reporting. I am following up internally and expect to have an update next week.

@Ann Worley I never received feedback on this. As a result, I am unable to report the problem and get help on the actual issue itself (i.e. how to hide the epic link field via field configurations).

Ann Worley Atlassian Team May 16, 2018

I found out that customers are now encouraged to raise support tickets so the support engineer can open the bug report. If Morgan's answer doesn't address your question and you still feel it's a bug I will be happy to open the support ticket on your behalf.

@Ann Worley thanks for the feedback. I will try to discuss the actual matter here for now. 

Not sure how the intended Atlassian workflow is for customers with starter license. I thought these customers cannot raise support tickets (they should go to the community instead), which also blocks them from filing bug reports.

Ann Worley Atlassian Team May 16, 2018

No customers can directly file bug reports any more: Where do I report a Bug to Atlassian? 

My understanding is that we like for Atlassian support to file the bugs now so they are validated and contain all the info the devs look for to come up with fixes. I am part of the support team and am happy to open bugs and suggestions for customers on Community, regardless of license or if the customer is user or administrator. Sometimes it is necessary to use the support portal, i.e. open a ticket on the customer's behalf, in order to share logs or confidential materials.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

229 views 1 2
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you