RELATED IDEAS
Allow for a check list to be copied to the GitHub product AND not change the check list in the originating work activity.
The check list (versus ordered / unordered list) in the text field is very nice. However, integration process translates the Check List to an unordered list in GitHub and then updates that back to the originating work activity. This process changes the original check list in the work activity to a unordered list. Not sure if this constitutes an error, but it appears to be inconsistent at a minimum.
My Reason: Why have a check list initially in the work activity just to have it change to a unordered list. It's O.K. , I guess, to have a unordered list in the GitHub issue, but to have it changed in the work activity... not good.
It would be great if the check list would be consistently used and updated throughout all the different records.
© 2025 Aha! Labs Inc.•All rights reserved
That lack of this makes checklists unusable when working with GitHub. My organization make extensive use of checklists in GitHub so this is a big problem for me. The only alternative is to map checklists in GitHub to Research items in Aha, but this then removes them from the Feature description in Aha and adds additional ugly formatting in GitHub. This is overkill and unusable when all I want is a description and list of things my team needs to check off during development.