Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Exclude Code/Credentials in e-mails

Hello,

What is the best way to hide/exclude sensitive information from JIRA emails (ticket updates, etc)? It's a security liability to include stuff like keys, code, passwords, etc. on emails; but I don't know what can be done to avoid this issue without disabling email notifications.

1 answer

1 vote

There's no code for doing that in Jira, because there's no way to tell it information is sensitive (other than to use simple security to protect the entire issue)

You're looking at the wrong part of the problem though.  There is no real technical solution, and if your people are putting sensitive information into Jira, you have to assume it's compromised already.

The real solution is to get your people to stop publishing it in Jira.  You actually have a security issue here, and it needs to be fixed by prevention, not "closing the door after the horse has bolted"

Payne Community Leader May 19, 2021

Our organization had a small problem with help desk staff putting passwords in issues, and we resolved it exactly as you state, simply by user education. Not only should information like that not go out in emails, the topic of the original poster's question, but further, it should not be in Jira, period, where many more eyes than are necessary have access to that information.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you