RELATED IDEAS
Require fields by status
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.
The additional issue is that my JIRA workflow configuration requires these fields by status, so if the status changes in Aha!, if these fields are not filled, the sync fails because they are now required in JIRA.
I would like to be able to designate fields as required by status.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +85
61
MERGED
Create conditional required fields
Many times , We need additional information depending on certain workflow states or other information. Ideally there would be a way for us to have a field that is required after a certain value is set. Examples - - On an idea, when we say that som...
2
Future consideration
13
MERGED
3
MERGED
On Change of state implement ruleset on fields
What is the challenge? When a state changes other fields my need further information to be updated. What is the impact? Synchronisation to other tools like ADO becomes a challenge with required information missing. Describe your idea on change of ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
Agree with all below comments this is a must. Many users don't pay attention to integration failures. This causes Aha and ADO for us to be out of sync. Adding a comment through automation could be useful here but unfortunately you can't @ mention anyone in the comment. Sending another email also isn't great since it is an email and you can't send it to the user who flipped the status, only creator or assigned user options are allowed. Please address ASAP!
This would be very helpful in ensuring our data quality in Aha! and the reliance on the data. Thank you.
We make some fields required because the corresponding field in an integrated system is required. Allowing users to clear the field value then stops the sync, so the records are now out of sync. Our end users find this SUPER frustrating.
Its definitely missing logic here
Its required during create but it can be removed later, whats the point of being it required? there's no logic to make a field required all time.
There are some cases, where we don't need to fill in a field at create but required later when it enters a certain state.
Having it only at create forcing users to fill in some random value to create a feature just to bipass it.
I need condional fields to make ideas sorting more comfortable. Instead of having 10 fields at once, I want to have initial choise of 3 items (Marketing, Product, Process complains). For example, if you select Marketing, appears a choice of
- Activation
- Subscription
- Update
- etc
If Product issue is chosen, then showen choice of
- Freezing
- Rendering
- etc
Yes please - I need certain fields to have a value before moving to a new state. For example, making sure a Feature is assigned a Release before moving to a "Ready for Development" state.
Mandatory fields on Jira must be inherited through the integration to Aha to allow proper issue type handling ( e.g. prior to closure of an EPIC, our Jira mandate to set resolution field first ) – otherwise, it’ll create constant sync issues
To me, this seems to be like a bug or lack of basic functionality on aha
Definitely a need - especially when you do have integrations that become not useful as most users don't pay attention to any sync failure - admins have to monitor through the issues and it's not worth the time and effort when you are using in large implementation.
This is great! I would also ask that if we FLAG a story as BLOCKED (Similar to JIRA) that the system requires you to populate a Blocked Reason
Dates and estimates are fields that come to mind specifically.