Status Future consideration
Categories Features
Created by Bonnie Trei
Created on Oct 29, 2020

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.

  • Attach files
  • Joel M
    Oct 30, 2020

    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

  • Kevin Morgan
    Oct 29, 2020

    Dates and estimates are fields that come to mind specifically.

Conditional work flow

Merged
Its really badly needed to be able to build conditional workflow using custom fields and application fields.
Antonio Beretini about 6 years ago in Application 6 Future consideration