RELATED IDEAS
Allow multiple primary record types (i.e. Features & Master Features) in list reports
I want to show a list of all features and some of those features have master features. It is redundant (especially for those with share the report with) for the children features to seemingly appear multiple times. This would be most useful for features, master features, and initiatives. I understand for it not applying to releases, and goals.
However, I can see a case to have goals and initiatives in a similar view.
Exactly what I need as well to combine Features and Master Features (Epics) into a single view.
Ok, thank you for sharing the additional context. That is very helpful.
The reason this is not currently possible is because these are different record types and thus different fields (even though they may be named the same.) At this time, we do not have plans to allow consolidating multiple record types like this in reports. But we will continue to monitor customer feedback on this.
thanks for the response, but it's not quite what we're looking for. it would be more like this:
Feature/Master Feature
Relevant fields (i.e. Status or Assignee)
Feature A
Completed
Feature B
In Progress
Master Feature 1
In Progress
Feature C
In Progress
Master Feature 2
Not Started
Initiative X
Not Started
It may not be relevant or feasible to necessarily have those types of "parent" or "related" links, but fields such as Status, Assignee, Description, etc. would be really useful to have in a single list view, regardless of how large that particular effort might be. If there's a way to include those other links, that's fine but not what I'm attempting to accomplish here.
Thank you for your idea. Can you share more details about the view you are trying to create? If my understanding of your use case here is correct, then you should be able to create this now.
For example, if the report you need is:
Feature name
Master feature name
Feature A
Master feature 1
Feature B
Feature C
Master feature 1
Feature D
Master feature 2
You can create this by making features your primary record type. In this case, features should not be duplicated.