I'm not sure what would work best here. I don't think that the script should necessarily close the synced task when the original is closed, but it would be nice if there was some way to easily find out about them.
A few options off the top of my head:
The separate script which produces a list seems like the easiest.
If we get into syncing "updated" information from upstream tickets into downstream tickets, we might as well go full-bore and start copying comments from upstream to jira too. The logic would be similar and it might be easier to write if generalized.
Separate script is certainly fine.
I guess I wouldn't necessarily be opposed to a comment sync, though that would mean a lot of duplicate emails. Would be interesting to see how the other users feel about it
Four months later, and I've changed my mind again. :s Users have expressed interest in copying comments (in #6).. and, if we get into that we might as well get into trying to synchronized the "closed" status from upstream to downstream too.
One tricky problem here will be that the "done" state in JIRA needs to be configurable per-project, since different projects may have different workflows with different "done" states.
Since the discussion occured 5 months ago, Is there latest update recently? Can any of proposed solution can deployed with Koji sync script?
@ralph hello, any update on this issue please? My team has a big traffic of GIt-to-Jira tickets and we would appreciate it if a Jira ticket updates its status as closed or gets a label when the original Git issue is closed.
No updates here. I currently have zero resources available to support adding new features to sync-to-jira.
I can accept patches, though!
Closing this issue as this feature has been added (see PR#65)
Metadata Update from @sidpremkumar: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.