Features

It's currently possible to create a new release in a new workspace that is a copy of a release in another workspace, which will also copy all of the features within that release. If I need to copy a single feature to a new workspace, though, I hav...

When viewing the User Story/Feature board, it would be great to be able to color code the Epic nested above the User Story. This would help to be able to visually differentiate all User Stories that are associated an Epic. The user should be able ...

Currently, record relationship field types can't be sent to Jira. We'd like to be able to see these fields in Jira so we can report on them.

What is the challenge? Work remaining and over capacity indications of a release remain the same despite filters What is the impact? Unable to easily sum ask of teams in board view Describe your idea work updates to sum ask based on ...

Part of our process for writing features is to essentially create a living document using the feature layout and custom fields. We created a Use Case(s) custom table that we turned into a one-to-many relationship custom field as each feature could...

I'm using release phase as my "sprints". When creating features, sometimes I want to add them directly into the sprint as they are being created. Right now it is a bit arduous to not have that field at my finger tips when creating features with th...

The trouble is that when you plan a feature into release R1 with capacity C1, it is not a super rare situation when after execution of that release (when collecting data from requirements as "work done" and "remaining effo...

What is the challenge? What I am observing is that progress on roadmaps appears to be measured based exclusively on detailed estimates as Actual/Detailed estimate. This works great for things that have detailed estimates, but much of our future as...

What is the challenge? If you are using a feature as a template for repeatable work and it includes a series of child requirements, copying the feature does copy the child requirements but any record relationship links between the copied require...

Currently, the list of requirements within a feature is fixed and only contains 3 columns: Requirement # Requirement Name Status It would be great if we could customize the columns to display. In my case, the status is not that important to see ...