- one of our CommTech herald rule H260 is broken (every time we move tickets they get removed from the kanban board), as the EM I would like to fix it, could you give me permission to do so?
- I would need to do this regularly that's why the permission would be beneficial
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
@Samwilson and @MusikAnimal within your team have access to fix it if it's urgent. They just need to add the Kanban to list of projects not matching the rule.
In regards to access, that should probably be a separate ticket. We shouldn't have please fix this issue that's blocking my team and please give my team access to sort it in future on one task.
Comment Actions
Hi, I edited H260 and added "Project tags include none of: Community-Tech (CommTech-Kanban)" as a condition. If I understand correctly, this should fix the problem.
According to the history of H260 , MusikAnimal has added the "latest" sprint project as an ignore condition in the past. (See e.g. T292112 for a past request to update this rule and make it deal correctly with sprint projects.) Members of acl*phabricator can edited global Herald rules - if you'd like more people added, please file a separate ticket. Thanks!
Technically speaking, implementing T144041: Avoid the need to update Herald exclusion rules everytime a new milestone is created would "fix" this issue.
Comment Actions
@RhinosF1 I don't have access to edit that rule (clicking edit just gives a permissions error: "You do not have permission to edit this object.").
Comment Actions
It looked from the history like you'd done it before. Didn't realise you might have lost access.
Comment Actions
Thanks for looking at this, yeah, maybe it wasn't that urgent, sorry for that, I just knew it takes another 6 hours until Leon will be around and we might have accidentally lost track of some tickets. Maybe it wasn't completely appropriate.
Comment Actions
See https://www.mediawiki.org/wiki/Phabricator/Project_management#Priority_levels
Just create a task requesting access to #acl*Phabricator and state the Phabricator username if those that need it. A short reason should be given.
Comment Actions
I'm confused what the problem is, but if I caused it, allow me to apologize!
Hi, I edited H260 and added "Project tags include none of: Community-Tech (CommTech-Kanban)" as a condition. If I understand correctly, this should fix the problem.
According to the history of H260 , MusikAnimal has added the "latest" sprint project as an ignore condition in the past. (See e.g. T292112 for a past request to update this rule and make it deal correctly with sprint projects.)
Thanks for stepping in! Yes I think that was the intention, if I understand correctly. If tasks get tagged with the Kanban, it now gets duplicated at Community-Tech ? May not be what we want, but regardless I'm glad we got another team member who can change these things! We'll fix it further as necessary.
Thanks to all