As a product manager, I'd like to be able to bulk edit my master features.
This is needed. Huge. Huge need.
We love the bulk edit on features - really really need this for master features to be more useful.
Is there any update on this?
This is extremely important to have. We are using Master Features and it would be huge timesaver in managing updates and changes.
This is really needed
I agree, a must have feature. Any updates?
We have fields for each Master Feature that need to be filled out and I need a way to bulk-edit these by using a list. It's painful to go into each one manually to fill out the fields.
Yes please!! This would be incredibly helpful. I am having to manually move dozens right now and it's painful! I see this capability being critical to those who are new to the tool (like me) and have been figuring out their integration mapping with other development tools. Now that I finally figured out my mapping I need to convert a much of master features to features and it's rough going without a bulk edit.
I have about 50 Epics/Master Features that I have to update 1 by 1 or using CSV update. This would be a monster time saver!
We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the same release, we get 10 different releases in Aha.
It would therefore be great if we could map one Aha release to several fixVersions in Jira. The functionality could be similar to the already existing Status mapping for a Jira integration where it is possible to map one Aha Status to several Jira statuses.
This is needed in order for us to use AHA! successfully. We use Master Features as our primary tie to Jira's EPICs.
+1 We have fields for each Master Feature that need to be filled out and I need a way to bulk-edit these by using a list. It's painful to go into each one manually to fill out the fields.+1 This is needed in order for us to use AHA! successfully. We use Master Features as our primary tie to Jira's EPICs.
I'll jump on the bandwagon here and repeat that this needs to be done as soon as possible!
You won't be notified about changes to this idea.