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!


How to handle temp users during external system import

Ehren E
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 30, 2023

We are currently going through the exercise of importing several years of github issues into Jira, which we will use going forward.  We've written the scripts to export and transform the data to something that Jira expects.  The last piece is mapping the existing github users to newly created jira users.  

Our issue is that there are several "users" that are either no longer with our company, generic users used for some legacy purpose and bot users from various services we used.  These users made comments on our project over time and we want to maintain that historical relevance without having to dig back through old github issues.

Do I have any good options to map those users Jira?  Ideally without creating new users or through some temp user functionality?  There are lots of these users and I don't want to pay for them temporarily while we copy data over.  

Thanks for everyone's feedback in advance.

0 answers

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events