Currently when you bulk edit epics from a list report there is no option to update the calculation method for the date range. This does exist for features so it seems like it should exist for epics too.
Biplab Panda
9 days ago
in Features
0
Planning to implement
Specify which fields will and will not be copied when copying a Feature
What is the challenge? When a Feature is copied, any field that is filled in will automatically be copied over to the newly created Feature What is the impact? Although most of time this is ok, some fields are Read-Only and therefore cannot be cle...
Joe Wilkinson
about 1 month ago
in Features
1
Future consideration
Prioritization report should support displaying strategy fields with multiple records (goals, objectives, key results)
What is the challenge? The prioritization report cannot display strategy fields tied to multiple records (like goals, objectives, and key results). What is the impact? Goals, objectives and key results are vital reference points when determining a...
Nathaniel Collum
about 1 month ago
in Features
0
Future consideration
Issue Types - Add ability to move an issue type to another workspace
What is the challenge? Within JIRA sometimes tickets get logged against a product/jira project which is incorrect. In that system we can either Move the ticket to another Jira project, or Clone and move the cloned ticket to another jira project. I...
Logan Lim
6 days ago
in Features
0
Future consideration
I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...
Bonnie Trei
about 4 years ago
in Features
15
Future consideration
Option to not copy Requirements when Copying a Feature
What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...
Lorena Connolly
about 2 months ago
in Features
1
Future consideration
What is the challenge? Automations currently make it possible to pass values from one record to another, such as users and dates. We need the ability to set the same choice lists across records. What is the impact? We often plan our work by compon...
Nathaniel Collum
2 months ago
in Features
0
Future consideration
Trigger automations from an automated delivery risk flag
What is the challenge? When an automated delivery risk is flagged, I want to then enact an automation to trigger notifications and todos to key team members to address the risk. Today, automations only support the manual delivery risk flag. What i...
Max Robbins
about 1 month ago
in Features
0
Future consideration
Enable integration mapping for custom fields referencing custom tables
What is the challenge? We are using custom tables to define workspace specific values and a corresponding custom field to select the value from a feature. We also have a need to send the value in our integration mapping to Rally. Currently the cus...
Tracy T
14 days ago
in Features
0
Future consideration
Allow creating custom table records through automation actions
What is the challenge? Some advanced use-cases (such as tracking the history of a release assignment of a feature) are not possible today. What is the impact? This prevents users from tracking slipped work for work which has been re-assigned many ...
Alex Bartlow
about 2 months ago
in Features
0
Future consideration