We've heard from some of our clients how it would sometimes be useful for Pipeline Steps to be configurable on a per-Project basis. The common use case is the different Projects may not make use of all the Pipeline Steps configured for the site, and cutting down on clutter in any way possible is always welcome. What do you think? What are some other use cases out there? If you'd like to see this implemented, click the "Me Too!" button below.
Date
Votes
1 comment
-
Nate Barnard If we can group per project pipeline steps, can we please also include available statuses?
Trying to evolve our workflow from one project to the next and it's super tricky to keep the steps and moreso the statuses from being confusing and improperly used.
Please sign in to leave a comment.