You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have since removed epic name and epic link from the epic issue type and screen and any other issue type but the field is still present on the form and required.
How can I remove from the form but maybe keep under the issue view, if possible?
This is because Epic Name is a system-level required field when creating an Epic - you must have an Epic Name on all Epics.
So it will appear on the Request Portal regardless.
There might be an alternative, but it depends on what process this Request Type represents - could you give us some more details about how it works, so we can advise further? :)
Hey Stephen and thank you for the reply!
I have two forms on the portal which are integrated into two request types. The issue type for both of these requests is Epic.
If I'm understanding you correctly, I will have to change the issue type from Epic to another type in order to remove the required Epic Name field from the portal?
At this point in time - yes, that is correct.
You could do something with Automation though, if you need it to be an Epic post-creation - it might look something like this:
A few notes on this rule...
Let us know if this might work for you!
This shouldn't be the case - I tested this prior to recommending it.
Could you clarify...
It might also be useful to see a screenshot of the Action in your rule, to help clarify if there's any issue there :)
Hey Stephen, sorry for the late reply. If the form request type is anything other than Epic type then the epic name is missing, however, when testing the Epic issue the epic name is on the form even if I try and remove it. The epic name is still on the epic screen configuration.
The request types are setup the same with the same names. Not cloning at all but I am using a template app on the form so when an issue is created then a template applied with subtask. The template is already configured as an Epic so I wouldn't expect this to be an issue since we're trying to automate the issue to change to an epic.
At this point I'm going to change the template type and request type to not be Epic since I cant get around this Epic name field on the request form and test further