Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


One Organisation, separate departments


New here and configuring our Jira Cloud Service desk and Jira Software. I have two questions/discussion points I am interested to hear what people have done.

1) One organisation but different departments and I would like to ensure that each customer is separated into their departments so when I produce monthly reports I can deliver who has logged most tickets by department.

How are people doing this? Are people using Atlassian People to do this as Teams? Or is it a case of creating a custom field within the customer profile to record this?


2)Also we are moving from Zendesk which we have used purely as users emailing in so the portal will be foreign concept. So to transition we are allowing users to email and will then introduce the portal at a later date.

I don't think we'll ever remove people from emailing in so do you know if it's possible that when a emailed ticket comes in can you define it in to a specific issue type to ensure we're logging the relevant information or following the correct workflow?


Many thanks in advance.





1 comment


Log in or Sign up to comment
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 01, 2019

Hi Tom,

I'm taking a stab at this and coming up with a solution I haven't tested. 

I'll start with 2). You can use an automation rule that triages incoming e-mail requests into issues based on e-mail summary.

Additionally for 1) you could setup the automation rule above to match by reporter. You can choose person by person but also you can have a group.  On that rule you can add a label to the ticket, or you can populate a field you want that would be the department of that person. This way you could serve per reports based on users / departments / issue types.

The downside is that you need 1 rule per dept. Have a look at a sample config below.

Let me know if this works for you.





Automation Screen:

Screen Shot 2019-07-02 at 2.15.21 pm.png

Rule Config:

Screen Shot 2019-07-02 at 2.17.06 pm.png

AUG Leaders

Atlassian Community Events