RELATED IDEAS
Integrations 2.0: List view bulk edit Send to for integrations 2.0
Integration 1.0 integrations have the List view option for bulk editing Send to ----.
The integrations available to send to do not include 2.0 integrations.
2.0 integrations should be supported for bulk sending operations just like 1.0 integrations.
© 2024 Aha! Labs Inc.•All rights reserved
Thanks to everyone for your input on this idea. We are working to prioritize the ability to send records to the development system using bulk edit. In the meantime, it is important to know that you can in fact send records in bulk by sending the release or master feature. If you send the release, all master features, features, and requirements will be sent at once. If you send a master feature, all features and requirements will be sent.
How could you remove some critical functionality which was already available in 1.0? Product Managers will not spend time opening up individual features and then pushing them one by one. This is a must have functionality to use bulk edit for integration push. Please implement this asap.
Aha Team - If you are wanting customers to have high adoption and usage of your products, you need to make getting started easy. Bulk operations are critical for a large/high volume organizations. - Mimi, VP - Product
I have new products that consist of 60-100 epics each. Doing this manually for 60-100 epics vs. doing it once via bulk update is a MAJOR inconvenience. Please fix this.
This is a problem. We have our Engineering team review epics before syncing to Jira. They review a set of epics and after they will need to be bulk synced. Syncing them one at a time will be efficient and error prone.
This is more than inconvenient when trying to send several epics at a time x 100s of product managers. Not sure why this was not also included in 2.0 integration and would like to know when it will be available for my team.