Prevent users from inadvertently moving Features' workspace
Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
Guest
over 1 year ago
in Epics
0
Future consideration
What is the challenge? If I use a pre-defined tag list to encode information such as a stakeholder team, I have to select all of the teams above that one in the hierarchy manually to be able to report at various levels. What is the impact? If I ma...
Guest
12 months ago
in Epics
3
Future consideration
Enable milestone key dates in epic & enable to be used in custom roadmap
Our team uses releases by a timeframe, not by an individual product release. Thus our release is made up of multiple epics that need a milestone per epic. Please enable a milestone option at the epic level in both the epic & custom roadmaps to...
Guest
almost 2 years ago
in Epics
0
Future consideration
When we change Epics quarterly plan, user stories are being lost on the way
When we move Epic from one quarterly plan to another, if we drag them, it asks should the linked user stories be moved as well. However, if we simply change quarterly plan name in the field, user stories are not being moved. Same issue appears if ...
Guest
almost 2 years ago
in Epics
0
Future consideration
What is the challenge? When we do annual planning, we do it in the form of EPICs. We typically arrange these into one or more planning releases (e.g., 2025, Q1 2025, 2H 2025, etc.). At this stage few have features under them, which is fine. As we ...
Guest
4 months ago
in Epics
0
Future consideration
Allow "Original Estimate and "Logged Effort" to be used in Calculated Columns
In Roadmaps list, having the ability to do calculated columns is incredibly powerful. However, we recently noticed that there are two fields we want to use to create charts that are not available to use. These are Original Estimate and Logged Effo...
Guest
over 3 years ago
in Epics
1
Future consideration
When adding features to an epic, I should be able to select multiple Features
When creating an epic, that has features that already exist. Its not possible to add more than one at one time. This means that each time I want to associate a feature, I have to open the select "Add" then the modal will appear to select existing ...
Guest
over 4 years ago
in Epics
0
Future consideration
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
Guest
10 months ago
in Epics
0
Future consideration
Reload Configuration in an Integration Template using bulk edit via List
What is the challenge? When using an integration template to Jira in multiple workspaces and there is a change (e.g. adding a new field, remove fields, etc.) the propagation of the change does not happen automatically What is the impact? Time cons...
Guest
5 months ago
in Epics
0
Future consideration
Allow conversion of Epic to Feature when the Epic contains features
When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
Emily Yankush
over 2 years ago
in Epics
0
Future consideration