Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What is the best practice to track a limitation of a feature (epic) in Jira?

A feature request is created as an EPIC tracked in a separate project called FR in JIRA. What is the best practice to track a design limitation of the feature in JIRA?

2 answers

0 votes
Mark Cruth Atlassian Team Oct 29, 2020

Hi @Jeyesh Jeykhar ! Are you using Jira Align? If you are, there are are a couple approaches you can take. 

  • If you talking about technical design, you may want to create a custom field on the Details tab of the Feature asking the submitter to outline technical design limitations (something you can talk to your Jira Align Admin about adding to the screen)
  • If by design you mean things like UX design, you can use the Design tab on a Feature to outline this kind of information (if it's not on in your instance of Jira Align, ask your Jira Align Admin to turn it on)
    Screen Shot 2020-10-29 at 7.11.19 AM.png

No, we are not using Jira align. We are using only Jira

Mark Cruth Atlassian Team Oct 29, 2020

Hi @Jeyesh Jeykhar ! You're in the Jira Align space of Community - I would recommend posting your question to the Jira Community'll get better answers :-)

Good luck in your quest for knowledge!

0 votes

Hi @Jeyesh Jeykhar , when you are saying "design limitation", is it another type of Jira issue which has been created in a project different from "FR"?

@Deepanshu Natani, I am trying to figure out if creation of another project for Limitation is the best approach or if there anything else that I could do in the current project "FR" itself.

The end goal is all the limitation should be tracked as per release basis. i.e Each release will have a set of EPICs created in the "FR" project. I would also want the limitations to be easily documented and collected at the end of a release.

@Jeyesh Jeykhar, Do you see any problem if you manage all the epics, design limitations and releases in the same project?

You can simply create an issue type for creating and tracking your design limitations in the same project. If required, they can be easily linked with the epics and also assigned fix versions/ release.

As per the details shared by you, I do not see any reason to create a separate project

Like Jeyesh Jeykhar likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events