Hi Alex,

Thanks for your reply.
On one hand I tend to agree with you that the existing workflow tools could help an organization with the package promotion workflow. Sure.
On the other hand this strongly depends on how willing an organization is to have a dedicated workflow defined (and maintained) in the existing workflow tool.
If the organization states 'one workflow fits all' then I think the workflow tool should not be used and it would be great to have alternative available.

Cheers,
Paul

Hi,

Having the best practises as described in proget package promotion implemented I want to more in control over which packages have to be promoted.

At this moment I have a separate process in place in which in engineers can request a specific package-version in which certain criteria are being checked before the actual promotion can is done (or not). These criteria are described in a single (markdown) file.
This all works fine, but it is difficult to setup traceability from the request to the actual package promotion. (Multiple tools are involved causing unnecessary context switches.

This is where the idea crossed my mind if it is possible to have a kind of ticketing system added to proget that provides that supports this package promotion request process.
So basically a system to support the process of requesting and decision of promotion of packages.

(This ticketing system could be similar to the support-ticketing system currently available for Inedo products.)