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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

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

Radu Atlassian Team 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


Log in or Sign up to comment
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

175 views 2 9
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