You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have been toying around with Portfolio and have made a few hundred changes while I test out different scenarios. I don't want to send out a mass email with a few hundred updates, so is it possible to commit these changes to update JIRA without sending an email (similar to the bulk change functionality)?
The emails sent on commit are going to reflect the settings of your Notification Scheme on the connected projects to the modified issues, and you would need to identify the events triggering the notifications and reduce the traffic for those events as needed for your commit.
You could temporarily disable these notifications with one of the methods described in the following posts to get around this, one describes fully disabling email temporarily, the other is a temporary scheme with relaxed notifications:
@benclohesy I feel your pain.
@Earl McCutcheon how would you feel if you suddenly got over 2000 emails from your JIRA Portfolio admin sending out updates? Bulk updates in regular JIRA allow to not send emails, its a much needed feature for portfolio. Very frustrating to have a work around for something so critical in a bulk management tool.
Thanks for the feedback and this is something we are looking at implementing, and we are tracking interest in the feature at the following link:
Please add a vote to to show your interest to help bump up the priority as covered in the "Implementation of New Features Policy" and if you have any additional feedback please drop a comment on the feature request as well.
@Earl McCutcheon Done but again it's been open for two years and no change.
How on earth are other companies doing this with Portfolio at a bulk scale for enterprises without complaining though, the votes on the issue and conversation is so low..... I'm at a loss to understand whether you don't have any portfolio users trying to use it at scale as customers or whether people are simply happy to spam their teams with trivial update or hack their own schemas on an ongoing basis???