Thu, Jan 26
What for is "audit.can-author-close-audit" then?
You may be able to use Projects or Owners to create groups. Any member of a Project or Package auditor can accept on behalf of the project or package.
You could also add a condition like this to your rules which trigger audits:
he has to remove the group and add himself as Auditor
Standard workflow is:
- Herald adds a group of people responsible for the audit to every commit.
- An Auditor picks several commits (he has to remove the group and add himself as Auditor, so no other auditors pick the same commit at the same time)
- Then Auditor accepts a commit or raises a concern.
- When the concern is raised, the Author prepares a new commit fixing this concern with commit message "Depends on ..."
- Then the Author has to go to the Phabricator and change the state to "Needs Verification"; also he should assign this fixing commit to the same Auditor (unfortunately, I don't know how to do this automatically, via commit message or Herald).
- Now the Auditor can see both commits and can accept them.
Jan 12 2017
Closing for lack of feedback. You can make custom dashboard panels for whatever query / state you want to track.
Jan 6 2017
See also T4144#175505
Jan 4 2017
Slack has some nice color blind themes, which I use as my normal theme.
What color scheme would the user prefer?
Okay, after some tests, looks like the user has deuteranopia. Consistent with what you have there.
Of the four, this is the only type that's difficult:
Uh, I'll see if they can take an online test to narrow it down further.
They don't know what type they have more specifically than red-green, unfortunately.
There are 4 types of red-green color blindness, and they all work differently.
I went through color blindness simulators and I can distinguish every type using the supplied image. So without more information, I'm not sure how to proceed here. Why can't you ask them what type of color blindness they have, specifically?
I'm not sure I understand what you mean. To be clear, the user doesn't have an issue reading the text; they have an issue distinguishing between red highlight and green highlight. I think it would be even more confusing without any highlighting at all.
Jan 3 2017
hopefully not a feature request, thanks.
See Consulting if you'd like a one-on-one answer from the upstream.
Hey @epriestley, Ideally i'd just like to ask a question on where this feature has gone. I posted in the IRC channel but got no response.
Please see Contributing Feature Requests for instructions on filing a feature request which can become a maintainable feature in the upstream.
Dec 13 2016
Sep 6 2016
We haven't received more information about this in more than a month.
Aug 10 2016
Mar 29 2016
Root problem: To ensure quality software, I want to make sure that all reviewers accept a change.
Most likely your request is covered by other tasks.
Do you have blocking reviewers on these diffs?
I have read it, but after re-reading let me give this another go. My apologies, I know you guys are busy and I'm sitting here not knowing how to properly formulate a problem description.
I think that's just a rewording of the original description, and doesn't provide any new insight or context. It still focuses on a very narrow symptom problem (not being able to see individual reviewer status from the revision list), not the root problem.
T1279 is talking about the reviewer list on the detail page (/Dxxx), not the list page (/differential/). This was implemented years ago, so I suspect it isn't a duplicate, unless you're years out of date.
Mar 26 2016
This request doesn't describe a root problem, so we can't develop a solution to it. We haven't received any new information in more than a month. See Describing Root Problems and Contributing Feature Requests for help describing root problems and filing feature requests that the usptream can accept.
We don't have enough information about this problem to design a solution, and haven't received more information in more than a month. See Describing Root Problems and Contributing Feature Requests for details on how to submit an actionable feature request.
Mar 21 2016
Nothing actionable here, since we don't plan on adding additional options.
Mar 18 2016
Hope anybody can help on this.
Is it possible or would it be possible to create sub-groups with different rights?
For example I want to select only a bunch of users eligible to be reviewers and not all my users.
Feb 24 2016
We use a custom field release description of type remarkup. We then export tasks via conduit API to our HTML release notes. In this release description we use some of the remarkup feature set.
Feb 22 2016
Yes that should work for my use case - I've tested and verified this functionality. Thanks!
Feb 21 2016
We ultimately want teams to choose different colors so they can know which workboard they're on at a quick glance.
Yes, I concur, that would be useful.