This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-9965 Require fields by status.
Its really badly needed to be able to build conditional workflow using custom fields and application fields.
There is a variety of automation controls throughout the application. However, at this time, we do not have plans for conditional workflows between custom fields and application fields, based on current priorities and community feedback. We hope you can understand.
An example of why this would be helpful for us:
We have a custom field that indicates if our story was Planned (during sprint planning), Pushed (hotfix during a sprint), Pulled (had capacity to pull in another story), or Carryover (not finished during a sprint and needs moved to next sprint). When someone chooses Carryover we want them to have another field that is required have them choose the Original Sprint so we can track how many sprints a story gets carried over and is no longer on track.
Azure Devops allows us to mark certain fields as required before they can enter a status - this would be great if we can have the same functionality inside Aha.
Will the ever change?
For us, I can see enormous value in this. Because of the way that we have to manage our catalogue, we have "new ideas", "improvements" etc which need to go to different departments and may consist of different statuses. Ideally, we would want to be able to create a report which reflects this.
I'm not the person that left this comment... but... I could see workflows around status quite a bit. If the status of a feature is changed from X to Y then set a custom field to a specific value. Or if the age of feature/idea is greater than a certain age then change the status to on hold or needs attention.
I have a custom field coming from JIRA that tells me when dates are updated (don't get me started my DEVs are a pain and can't use out of the box JIRA fields grr), so one of the things I'd like to do is when that field changes values populate that value into the real due date field.
I can see a lot fo use for conditional workflows between fields.
Can you expand on what you would like to see here? An example would be helpful to understand how you would ideally like it to work.