Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thanks! A few quick thoughts:

- We've done exactly this for Github <> Tara. We have a bi-directional sync with Github issues, and active issues are converted into tasks in Tara. Basically, if a user wanted to, they could just use Tara as a Github issue tracker.

- We wanted to start with Github, then work our way through more git/source control platforms, and then move to Jira. Interestingly, structuring incoming data from Jira requires a few months of work on data models IF we don't want the user to spend a ton of time labelling. Jira's data structure can be a hot mess to deal with.

- If the sync took a day or even a week of configuration, would you find it worth your time to invest and go through that? Or would yo expect the sync to work instantaneously (like Github <> Tara).

- What would be your expectations on mapping for histories?




It makes sense that you started with Github. I agree too that Jira's data structure is a mess. I've managed one instance for years and any update was a whole mess on itself.

I think the sync configuration should be quick, something that can be bootstrapped like Trello integration with an export artifact.

About mapping for histories, it should be 1-to-1 and each spec to be a list point or a subtask. Nothing fancy nor complex if Tara is the main source of truth, leaving Jira as a way for non-tech users to report issues.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: