I am newer to Gerrit.
Recently, I am looking for a way to add custom fields to the "code review vote panel" of the Gerrit code review screen as below, after clicking the POST button, the values in these fields will be displayed in "History Block".
enter image description here
Is there a plugin or example?
I've spent a lot of time and still haven't found a satisfactory answer.
How can I do this?
Thanks!
Related
I would like to add a button (or a link) in the Gerrit change UI.
The purpose for this button is to extend the Gerrit UI for a specific copyright review by external reviewers (not part of the regular development team).
The idea is that clicking on this button would show up a dialog with options for severity level for the change (Trivial, Low, High). The user would select an appropriate level, and proceed further. It should then send an email with severity level and changes in the review to a predefined list.
I have added a custom label in the Gerrit review UI. The external reviewer can then give either -1 or +1 on the review.
Is this kind of customization possible in Gerrit UI?
I have looked at answer from gerrit-add-a-new-button, but couldn't find a definite answer.
Can someone provide a more detailed answer?
I use Gerrit normally for reviews, but don't know the advanced customization features associated with it.
Thanks for help in advance.
When a JIRA issue is assigned to me, I keep the issue page open so I can read fields, description, attachments, etc. But the problem is, any place I click, the fields enters in edit mode. I fear change anything by accident, so I was thinking if there is some way to put the ticket in "readonly mode", so I can change something only if I click some "edit" button, or visit a specific url. Is this possible?
There isn't a way to configure this at a user-level, but there is a project level setting to adjust on the applications settings page (if you have admin-level permissions for it). https://_your_url_.atlassian.net/secure/admin/EditApplicationProperties!default.jspa
Someone had requested this as a feature 7 years ago, but it seems like the JIRA development team has not actioned it. (as seen: https://jira.atlassian.com/browse/JRASERVER-29091)
I want to apply four eyes principle on gerrit. After reading the doc I found the example is already there. see the example. I just changed the example prolog a little bit: make the change submittable if the total score is 3 or higher, and remove the "verified" label.
After apply the new submit rule, new commits correctly get the "Ready to Submit" status after gets code-review score 3 or higher. however, the "submit" button is not displayed, even with the administrator account.
I am sure I have the "submit" permission set properly to that branch: If I remove the rules.pl file, the submit button is displayed.
In fact, I've tested all examples in the official doc. All has the same problem (Except for the Nothing is submittable Example because nothing is submittalbe, and the Reusing the default submit policy example because no rule is changed). What is the purpose of a "Ready to Submit" status without a submit button? I must be missing something.
I found little clue about writing gerrit submit rule prolog except for the official documents, which I've read intensively. Quite frustrated now. Any help would be appreciated.
I've been looking for a way to have a user acknowledge a
ticket after it has been assigned to them. I don't know if
this is a built in feature or if there is a plugin that
will create a state/button for a user to accept a ticket
after it has been put in there queue. I would expect to
see something like this from the ticket window around
workflow or start progress but no amounts of digging
through configuration settings has turned anything
relevant up.
Does anyone know about this added functionality in JIRA?
Much thanks.
I did this by a custom workflow step. After an issue arrived to an assignee (with status New) he/she should move it to another step (with status Open). Until he/she does it, the issue is considered as not noticed/reached the assignee. Also I have had a report showing issues with New status for more than a predefined period of time.
I'm not aware of a ready-made plugin which performs similar task (perhaps, I should dig into my posts on Atlassian answers to discover some clues for other solutions).
As #Stan says above, a custom workflow is the way to implement this. The workflow functionality in JIRA is very flexible and as a result has a bit of a learning curve, but Atlassian's documentation is pretty good. Post back here if you need help.
I have an blog where anyone can comment. I would like to approve the comments before they are published. I have a boolean field named "published" and I'm unsure what to do next. Can anyone point me in the right direction?
I can imagine several features :
you need to be be notified when a comment is created. If you're not expecting too much traffic, the application can notify you by email with the ActionMailer
you need an admin page where you'll see all the comments that are waiting from your approval. Use filters to ensure that only you have access to this page.
you'll certainly need to see the comments "in situ" before approving them. The blog page should display only "published" comments for average user, but for you it should display all comments, with a button to publish the ones waiting for approval.