Reopen merge request in gitlab - gitlab

Is there a way to reopen a merge request within Gitlab once it's been merged like there is with an issue?
In this example a merge request was merged before a code review and has been reverted, but it would be great to reopen the original merge request to keep the original history/discussions

There's Reopen merge request button in Gitlab (Checked with 10.3.4-ce, but appeared earlier). However it does absolutely nothing when pressed, even with commits added to the branch the merge request is tied with.

This is currently not possible. There is a feature request and someone already started working on it, but that work has stalled.
Currently the only option I see is to open a new merge request and link the old one. Probably not what you want, but easy to do, and at least the two MRs are linked.
I also looked at the API, whether it is possible to duplicate the old MR. While the API does allow you to add discussions, this is very limited. Especially as it is currently not possible to add discussions to a specific file and line number. It is not even possible to extract that information via the API.
Thus the only option to accomplish "reopening" or "duplicating" a merge request is to mess with the database or work on the merge request.

Related

GitLab block merge request if maintainer doesn't perform a code review and complete checklist

I am trying to set up a GitLab workflow for my project.
When someone writes on a feature branch and completes that task, that person creates a merge request.
In our team, we have created a checklist that represents the definition of done.
So when someone creates a merge request, one of the other developers has to do a code review and check all the items on the checklist.
Are there any tools for GitLab that will automatically comment the merge request and display the checklist in the comment. Also, the merge request should be blocked until another developer checks off all the items on the list?
We are a university research group and use a free version of the self-hosted GitLab instance with version 14.9.1

How to show Changes tab by default in GitLab merge request?

Is it at all possible to let GitLab show the Changes tab when browsing merge requests? It's very annoying to check a lot of merge requests when you have to switch to Changes tab every time.
Thank you

Delay in manifest changes or not seeing add-in at all

We are seeing an odd behavior where we update a manifest in production (basically remove the old one, add the new one) through EAC, however it takes more than an hour to take effect. My understanding is that the admin-defined manifests are stored in a particular System Mailbox, so I am confused why there should be a lengthy delay. Is there way to troubleshoot this, and (2 for 1) is there a general way to troubleshoot an Outlook App not showing up in, say, Outlook 2013.
This is the expected behavior, it can take upto 4 hours to get the latest manifest if deployed via EAC. Please have a look at comment made in this post via Sreeram https://techcommunity.microsoft.com/t5/Outlook-Blog/Centralized-Deployment-for-Outlook-add-ins-will-now-be-generally/ba-p/161164

using mail server to communicate with jira using api

im new to jira and its mail handlers.i want to use the jira's mail handlers to scan two folders in my mail box.and update two projects related to those folders. and i did that.
but now i want to extend that functionality.i want to keep the mails in those folders (stop mail handlers from deleting it after processing) and make it able to move issues/tasks across projects simply by moving the associated mail from the folder to the other folder. resulting in deletion of the original issue/task from that project and creating it in the other folder. please help in making this a possibility.
for those who didnt understand my problem: imagine im sending a cv for the post of php developer to a mail. when the reciepent checks it, he puts it in the php folder in his mailbox.so then a task is created in the project php developers. but next the reciepents thinks im more suitable in web developement rather than in php. so he just moves the mail from php folder to the web folder.so the existing task in php project gets deleted and a new task is created under web developement project. can i do this? if so how? please guide me..
Update
sigh..
i dont know how to work with corporate people. now the situation has changed. i hope you could help me with this one.sorry about the sudden change in the question..again...
now my boss wants sth like this.
i created a mail client using imap function to access mail services and retrieve those mails to a web function. theres no problem in that. but now my boss wants to handle jira through that same app aswell. means as like the my question when moving, putting a mail to a folder the app it self should comunicate with jira and make the necesary issue creation and deletion.. is this possible #Kuf?? if so please help. because my deadline is due Wednesday. and im almost there to panic..lol..please forgive me for changing questions like this. as it is not my will..
edit
I have seen that rest api does this. but how to use it? any answers?
The simplest way I found was to receive the emails in your main account and forward them to a second account, while saving a copy on the mail server. Than, tell Jira to pull the emails from the second email.
UPDATE
In the past, I've looked for a way to change Jira's email handler functionality, as you can see in this question here. It is impossible to achieve what you're asking using Jira's email handler because the way it works, it does not keep records of which emails were already read, Jira's service checks for new emails, ignores emails according the pre-defined filters (spam or user defined), handles the rest of the emails, and deletes them so it won't process them again.
The way I can think of to get the functionality you want is to re-write the email handler, you can get the source code, re-write it, and build it into your Jira app.
Another way, which i find easier, is to get all the emails into Jira, and from within Jira move the issues from one project to another. You can even create pre-defined buttons using Jira Scripting Suite to easily move issues between projects (create a post function and attach it to workflow transition).
If you need any help let me know. Good luck!
EDIT 2
Which Jira version do you use? which actions are you planning to do using the remote API? Jira REST API is the newest, but some of the old APIs have capabilities that are lacking in REST. To try and decide which API suits you, have a a look at JIRA Remote API Reference.
If you decide to use the REST API, I suggest that you read Jira's Getting Started with REST manual, which shows how to use the REST API. For the full documentation check out JIRA REST API documentation (make sure to use the right version according to your Jira version).

What is the perforce bug review or bug triage feature?

I want to have the ability in Perforce where when one submits code, instead of getting submitted immediately, a different Perforce user gets notified so that they can review the changes to approve them before they actually get submitted.
Does any such feature exist in Perforce? Would it require a plugin? Does that feature exist in any code repo software? How would one really accomplish something like that?
There's a whole category of code review tools, such as reviewboard, Reitveld, Gerrit, etc. Here's some links: http://en.wikipedia.org/wiki/Review_Board
I would do that using shelves.
http://www.perforce.com/perforce/doc.current/manuals/cmdref/shelve.html

Resources