Best Practices for Managing Git Issues in Conjunction with SaltStack Enterprise Support Tickets

SaltStack strongly encourages our Enterprise Customers to be part of the open source development process by opening Git-Issues and committing code.

By participating in the Git process, you directly affect the way open & Enterprise Salt is developed at its open source roots in the context of a community conversation. Many eyes; best code.

This being noted, even if you choose to engage in the open source process, as a SaltStack Enterprise Customer , we ask that Enterprise Customers open a SaltStack-Enterprise-Portal ticket that references the Git-Issue under discussion.

By opening a SaltStack-Enterprise-Portal ticket cross referencing the Git-Issue, this enables the Salt Support, Development & Product Management team to give the given Git-Issue top priority, rather than letting organic forces be the sole driver of the remediation of the given bug or feature request.

Once an Enterprise Customer has opened a SaltStack-Enterprise-Portal ticket that references the Git-Issue, the Salt-Support-Team with apply the “ZD” Git Label to the Git-Issue, along with the Enterprise-Portal ticket number, to ensure top prioritization of the issue. Once done, the issue will be tracked in both Git & SaltStack-Enterprise-Portal.