Store Milestones in journal - Ticket style

[paulsputer]

While working on #1048 for ticket references I notice that ticket/milestone relationship could be described via a new reference type. This would then allow a milestone to be stored and represented as a ticket so as to use the same code and provide more options for improving user experience.

This would support #1014 and further tickets for task management and resolve workflows such as #1078

@gitblit any foreseeable disadvantages to this?

[gitblit]

Your description is a little abstract, but I have no conceptual problem with modeling a milestone more like a ticket. It sounds like a good idea and one I never considered.

The main trick is to make sure it behaves consistently across the different backends and to consider what (if anything) would need to be tweaked in the migration process. i.e. you should be able to start with a filesystem backend, migrate to a branch backend, migrate to a Redis backend, and, for good measure, return to the filesystem backend. That roundtrip (as far fetched as it may be) works now - but TBH may not work with the milestones as defined currently; I can't recall. Your idea may make that migration more seamless, if milestones are not already considered.