Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,966
Community Members
 
Community Events
176
Community Groups

Issues with adding a permanent CC in our project

Hello! I want to know what's the best way to add a permanent CC to our project. The client we're working for needs to collect the issues they send us via email and they need them to have them collected via cc in their ticketing app (via cc)

We need the best way to do this, I'm trying to add it via custom field with a user field, but it didn't work as I wanted to, because the email didn't got to my inbox when I was doing the tests. I'd better want them to be added as participants.

Is there a better way to do this? Thank you in advance!

1 answer

1 accepted

1 vote
Answer accepted

edited….

I just saw that you are on server. As such I doubt you have automation for Jira. However if you have any type of Automation or scripting add-on you should be able to keep the same thing.


Have you tried using Automation? I would simply set something up where shoe is created he would trigger can you set up any conditions that are necessary to perform the action. The action will simply be to add the email address (Customer) as the request participant. This should ensure that every issue meeting the conditions would have that customer as a request participant which results in a cc email notification. The one downside of this however, is that your customer may not want to be notified on every single update.

Actually, this is what my boss and what they have requested because they want to have a reaaaaally specific follow up of what we're telling them in their app. I'll give it a try. Thanks!

I'll leave this open a bit more in case there's more info while I try it.

This kinda worked! I'll look more into it! Thank you! 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events