Version control for tickets? [closed]

问题:

Conceptually related to the independent content-hosting with Git here.

I would like to separate 3 things: ticketing -version-control (management), programming -version-control and structural -version-control (more here). Now everyone should be able to see tickets and how they have evolved from an idea into a code/product. Currently, I have large problems because tickets are in proprietary coffins in Bitbucket and Github, apparently their business strategy to lock users. I want to manage my tickets in some repository -- related tickets here, here and here. If I do a ticket, I want to commit that. I want to keep track of my tickets also because I want to be able to change the provider later easily. Github has some good features such as punch -cards (more here) but otherwise harder to use over Bitbucket. I want to control my tickets and add features whenever I want to. So how can I have a version-control over tickets?

   |---> tickets' version-control (Ticgit -version-not-yet-exist)
   |
---|---> code's VC (git)
   |
   |---> structural VC (? maven ?? runs, deployes, ??)
   | 
   |---> perms' VC (Gitolite)

Perhaps related

1. Version control for version control?

2. Structure of Projects in Version Control

3. https://stackoverflow.com/questions/4952/database-version-control

回答1:

I'm not sure exactly what your question is: it reads more like a statement of intent than a question. But assuming you're looking for a system that lets you do that, you might be interested in ticgit, a bug-tracking system that uses a Git branch as a backend, letting you fork and branch the bug tracking data at the same time as forking the code.