I want to create the same comment on multiple features (sometimes epics) - It would be great if I could do this using Bulk Edit! Would still want the ability to @tag someone in this type of bulk edit comment area.
My use case - as an idea manager, the influx of new ideas overachieves my capacity to update, so I want to mass update comments to acknowlede that I received the ideas, or reviewed the ideas but want more info., or just add 'your idea will be reviewed shortly", so that the stakeholders who enter the idea just don't think nothing is happening.
My use case is less on Initiatives, Epics, etc. but being able to Bulk Comment on Ideas. Especially during a bulk close event. Ideally it would be partnered with ability to comment public/private.
Another use case: We are pretty aggressive with marking ideas that are poorly written or not clear enough to action as not in scope. We'd like to inform users about why we're changing the status, but it's the same message each time. There are not enough options in automation to allow us to do it through automation, so we'd like for our PM teams to be able to do it without needing to do so one at a time. This would really help us with our idea maintenance.
I concur - the related item had several votes as well. However, the csv is not as intuitive, especially when you would not be doing this often (compared to general bulk edit usage), takes the user out of their workflow and imports always inject more risk of doing an update incorrectly.
The need is not just comments - it is bulk edit with a public or private comment as well as an admin comment.
I voted on a different idea for this same issue (APP-I-5500). The response on that issue was that we can use the CSV import feature, which seems really inefficient. There were 11 other users that voted on that idea. Please consider transferring those votes to this feature as well, so that it has the appropriate weight.
For the record, this is my latest comment on the other issue:
If I'm already updating other fields using "Bulk Edit", why should I have to use a cumbersome CSV import workaround in order to add a comment to the issues I'm already updating? This is an extremely inefficient use of time. Frankly, it's easier to just go into each issue and add the comment. Please reconsider adding Comments to the Bulk Edit feature.
Hi Austin - it does seem like that would work however not for our exact use case, which is when a feature gets updated to ready we @tag the individual person on the IT team that will be pulling it into development. So the automation sounds nice but I doesn't exactly fit this purpose since it wouldn't be the same @tag every time you update the status.
Thank you for your idea. Would you be willing to share more details on your use case? I am curious if this may be a case where automation could be useful. Thanks!
Add option to add comments when bulk editing ideas
Merged
What is the challenge? Have to put same comments one by one in very idea What is the impact? Takes a lot of time and is very tedious Describe your idea Add an option to add comments in bulk editing pop up.
Abhishek Jain
3 months ago
in Ideas
1
Future consideration
1
MERGED
Adding Comment field as Bulk edit option
Merged
Can the comment field be added as an option for bulk edits? It is not currently available. There are often occasions that multiple records need to be updated with identical comments. It would be helpful to have the efficiency of using the bulk e...
My use case - as an idea manager, the influx of new ideas overachieves my capacity to update, so I want to mass update comments to acknowlede that I received the ideas, or reviewed the ideas but want more info., or just add 'your idea will be reviewed shortly", so that the stakeholders who enter the idea just don't think nothing is happening.
My use case is less on Initiatives, Epics, etc. but being able to Bulk Comment on Ideas. Especially during a bulk close event. Ideally it would be partnered with ability to comment public/private.
Another use case: We are pretty aggressive with marking ideas that are poorly written or not clear enough to action as not in scope. We'd like to inform users about why we're changing the status, but it's the same message each time. There are not enough options in automation to allow us to do it through automation, so we'd like for our PM teams to be able to do it without needing to do so one at a time. This would really help us with our idea maintenance.
I concur - the related item had several votes as well. However, the csv is not as intuitive, especially when you would not be doing this often (compared to general bulk edit usage), takes the user out of their workflow and imports always inject more risk of doing an update incorrectly.
The need is not just comments - it is bulk edit with a public or private comment as well as an admin comment.
I voted on a different idea for this same issue (APP-I-5500). The response on that issue was that we can use the CSV import feature, which seems really inefficient. There were 11 other users that voted on that idea. Please consider transferring those votes to this feature as well, so that it has the appropriate weight.
For the record, this is my latest comment on the other issue:
If I'm already updating other fields using "Bulk Edit", why should I have to use a cumbersome CSV import workaround in order to add a comment to the issues I'm already updating? This is an extremely inefficient use of time. Frankly, it's easier to just go into each issue and add the comment. Please reconsider adding Comments to the Bulk Edit feature.
Hi Austin - it does seem like that would work however not for our exact use case, which is when a feature gets updated to ready we @tag the individual person on the IT team that will be pulling it into development. So the automation sounds nice but I doesn't exactly fit this purpose since it wouldn't be the same @tag every time you update the status.
Thank you for your idea. Would you be willing to share more details on your use case? I am curious if this may be a case where automation could be useful. Thanks!