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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

Default organization for all users

We are using Active Directory to manage users for Jira. All users are, by default, clients to the service desk. If we want to all users to share issues, within the enterprise (and not the world at large) we want to use the restriction, "user can share with organization". 

There is no default organization (why not?), so I have created one. There appears to be no solution for assigning all jira users, all AD users, all members of the domain by email address or any variation. This seems to leave me manually adding each current user, which will send them a confusing email, then adding each new AD user when they are created and removing each AD user when they leave the organization. 

Is it really this cumbersome or am I missing something. I am going through the documentation but it seems to talk ABOUT users and organization without giving much concrete information about actually managing this. 

1 answer

Hi @Allan Ross

Yes it is irritating that Jira doesn't have a user group and organizations associations. Nor email domain and organization association. Altho it is a basic feature in many other service desks however it is missing from Jira. 

The easiest way to achieve this on Jira is to use an app like

  • Tinker for Jsd
  • Feature Bundle for jsd
  • Jira script runner

Suggestion, You may disable jira email when you add all users to an organization in the beginning

So the options, to implement a very basic feature, are:

1. manually enter every email address and manually maintain the list as users join and leave the organization.

2. paste the initial list of email addresses and then manually maintain the list as users join and leave the organization.

3. Pay for a 3rd party product and learn how to use it to determine if it is the right tool for the job.

And I suppose 4. get a better ticket system.

There's no harm in upgrading your infrastructure. However you may find a better substitute for JSD, but it won't be long until you reach a new limitation!

I've helped so many organizations with their with their ticketing system, and I stumbled across alot of limitations on each tool, however the beauty about Jira is there was always a workaround. It might cost you some dollars sometimes, it might need a littler learning. but at least in the end you will be able to have it!

I hope you go for Tinker for JSD since it is the cheapest and the easiest. And it is our plugin :-) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
4.1.0
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

165 views 0 4
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