Attributing issues and comments when migrating from Jira #42402
Replies: 3 comments 5 replies
-
I have the same issue. |
Beta Was this translation helpful? Give feedback.
-
For the record: we migrated using this script. Migrated issues can be seen here. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi all,
At Apache Arrow we're migrating from ASF's issue tracker to GitHub issues.
We have a good mapping of usernames between the two systems and would like to assign the issues to correct users when migrating if possible. We noticed Python migrated recently by creating Mannequin users. Is this something we could use as well or would we require an enterprise account?
We did notice mannequin users are documented in the grapql API, but there seems to be no way to create them with the API.
Which way would be best for us to pursue?
Best,
Rok
Beta Was this translation helpful? Give feedback.
All reactions