Allow selection of "Release" in the CSV Import file
Currently the "Import from CSV" functionality requires you to select a release before you select a file to upload. This creates a lot of overhead when importing a lot of Features of Epics that align with multiple Releases. Having the option to inc...
Karla Johnson
over 3 years ago
in Account settings
0
Already exists
Allow non-administrative (free) users to add open-ended info when responding to editable tag questions.
When sourcing info, tags are useful for creating consistency, by providing predefined responses. However, these are unable to capture responses that may diverge from the norm. We need to understand the norms but ALSO want to know when individuals ...
Guest
over 3 years ago
in Ideas portal
3
Already exists
as an executive, I'd like to be able to easily reference goal or initiative with a short name such as G-20 or INI-15
so that we can easily reference goal or initiative on a slide, without having to write out the whole name.
Something like G-1 for goal number one.
Current long (10-digit?) names are not usable for this purpose and are impractical.
You alrea...
Guest
almost 7 years ago
in Strategy
0
Already exists
The status should be applied to a BR (feature) when a Need (epic) is changed or ask if we would like to align. I find much time is wasted doing this and often BRs are missed.
Guest
over 3 years ago
in Releases
1
Already exists
Some of our project teams perform work for product teams where they wish to present their project roadmap to include specific tags on the bars similarly to how these are added to Feature cards (for example)
Guest
over 3 years ago
in Roadmaps
0
Already exists
Remove Epic as mandatory field while a feature is created.
To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
Guest
over 3 years ago
in Features
0
Already exists