Hi all,
I just got off an onboarding call with @Amy.from.ZenHub and discovered some missing features in the product that I need to work around in order to get ZenHub working for my multi-disiplinary team.
One of the take aways was in order for me to use workspace filters affectively I would need a way of automatically assigning labels to issues. Essentially adding them to the workspace view or filtering them out. Unfortunately ZenHub does not have this functionality, so after Amy pointed me to the ZenHub API I saw I had 4 web-hook events I can lift off of ZenHub and use these in zapier to create some basic PM rules.
Heres roughly what it looks like:
(removed media)
and the first path:
(removed media)
Something worth noting is that this uses Zap Paths which is just a conveniant way of managing the logic of all 4 event types in one Zap. But if you didnāt have the Paths function you could just make 4 zaps with filters on them based on the event type.
Obviously this will get more complicated as I ad new labels/workspaces.
But for now this does what I need and bandaids the lack of Label assignment rules in Zenhub until it can be incorporated as a native feature.
For anyone wondering why I need this - TLDR I donāt want to have to teach everyone how to use everything in ZenHub/Github. The Devs will get it but other stakeholders should just have to concern themselves with restricted/constrained views.
Hope this helps some others 
WTF is there a reason I canāt post images AND links here???
2 Likes
*AND Wait you also canāt edit your posts???
Why would you setup discourse like this? Itās just frustrating and makes me not want to use it.
2 Likes
Hi Dan,
Thanks for your insights there! Super useful points.
Regarding being able to post links and images, this is allowed once you move up one trust level to āParticipantā. Thereās more information on how to move up trust levels here in our FAQ. Weāve configured it this way to prevent spam posts and keep our community a safe space.
As for editing your post, you should have the ability to do this at any trust level. Thanks for pointing this out! Please bear with us while we look into this.
Jess
1 Like
Oh yep makes sense.
Refering to tha FAQ in the error message would have been super helpful/less gas lighting.
Regarding editing - the only thing I see when I click the 3 dots is the trash can.
Hey @agentlewis, welcome to the community. One possible solution to label assignment that I havenāt seen mentioned yet is GitHub Issue Templates. These can be set up on a per-repo basis and can be configured to have labels assigned automatically. You canāt force people to use them because the āNoneā option is always available, but this could be something close to what youāre looking for. Iāve included a screenshot below of what it looks like when creating a new issue in the ZenHub web app.
5 Likes
Oh yes that is definetly an alternative solution.
Iāll likely use this in combination with the zap automator (just finished debugging it)
Unfortunately I canāt share the zap as a recipe as it uses Paths and Code steps which you canāt shareā¦
Iāll make a video of it and post it here at a later date.
4 Likes
Using issue templates would also be more useful once GH moves their Form Templates feature out of the beta restriction limiting them to only public repos (a non-starter for my team).
This does make me think more about pipeline automation options which Iāve found myself reaching for and would find useful, namely - Workflows based on label & repo filters. E.g. āI want all new issues labelled with bug to be moved directly to my āInboxā pipeline AND I want all new issues labelled with feature request to be moved directly to my āFeature Requestā pipelin.ā, āI want all new PRs in the ādocumentationā repo to be moved to my workspaceās āIn Progressā pipeline.ā, "
3 Likes