I want to migrate from the clubhouse to JIRA with my all projects, EPIC and story points.
I built an application that does the job seamlessly. It will be available on the Jira App Marketplace shortly.
This is interesting.
We are migrating, but I've only migratet (manually...) a few ongoing projects.
An app to automagically migrate the entire project library from Clubhouse to Jira would be great.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Taiwo Ojo - do you know when this will be available? It sounds like a great app
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any word on when you might release this tool? If you have chosen not to release it, would you be willing to share the code?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are also migrating a project out of clubhouse and have most of it, but comments aren’t included in the export. Has anyone gotten those to come out in any export?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@jay modi did you solve this?
We are too considering a move from Clubhouse to Jira, not because Clubhouse is bad but we need more features that Jira can offer but Clubhouse can't.
Would be good to do the move automatically or semi-automatically...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You run into a few issues doing it this way, it's a heavy manual overhead to try and mark up text, de-emojify, and align config.
This is a process I have created a scalable solution for and will deploy an app to the app stores soon however happy to provide guidance and support to anyone that's currently migrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Taiwo Ojo. I'm about to embark on a Clubhouse to JIRA migration and am curious how far out you are from releasing your app?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here @Taiwo Ojo is this released?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any update on the APP for this migration ? I am still trying to find out how to migrate comments from clubhouse to JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Taiwo Ojo Do reply, please. I have tried 4th time today to migrate the issue but it is anyway failing to throw this error
```
Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: Caught PSQLException for insert into "public"."customfieldoption" ("customfield", "customfieldconfig", "disabled", "sequence", "customvalue")
values (?, ?, ?, ?, ?): ERROR: value too long for type character varying(255)
```
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Yashwardhan Pauranik : I'm seeing the same error exactly when attempting something completely different ... importing Jira Server project data to Jira Cloud. I'm not having any luck finding the culprit in the data. Did you ever learn anything regarding this error that might be helpful?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Yashwardhan Pauranik This error is caused when we have values that exceed the max character length.
While importing text fields (except Summary) the importer will import that record with a warning.
But when we try to import an option for a select list exceeding 255 characters, this error will be thrown.
(I figured it out when I was importing values for a multi-select field, but the data given to me had separated the values using semicolons, so all values were considered as a single string, and ran into this error.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.