Skip to Main Content
141 VOTE
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
  • Olena Korolova
    Reply
    |
    Jan 16, 2024

    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

    2 replies
  • Guest
    Reply
    |
    Dec 2, 2022

    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.

    2 replies
  • Guest
    Reply
    |
    Nov 15, 2022

    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


  • Karie Kelly
    Reply
    |
    May 28, 2022

    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.

  • Joel M
    Reply
    |
    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
    Reply
    |
    Oct 29, 2020

    Dates and estimates are fields that come to mind specifically.

  • +51
61 MERGED

Create conditional required fields

Merged
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...
Gilly Dekel about 2 years ago in Application 2 Future consideration
13 MERGED

Conditional work flow

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