Often you need to manage a set of consistently repeating events, where multiple issues are used to track the combined activity of a team. This page describes how to utilize GitLab Issue Import and a few spreadsheet tricks to make it possible to create a repeatable set of issues for future projects.
Import CSV button is at the top of the GitLab project issue list. This feature can be very useful for repeating projects with similar groups of issues / work.
You're familiar with the GitLab structure of how projects, groups, epics, milestones, issues, and labels work. If not, please review GitLab 101- No Tissues with Issues
You're comfortable working in a spreadsheet and using formulas to concatenate text into a cell. note: In my examples, I use the
& operator, which is the same as the
You have Developer permission level or higher in your project. (required to do issue import)
Your issues will be created in the same project (you can still do this for cross-project templates, but you will need to upload a separate CSV for each individual project). For example, if your template would require issues to live across Global Content, Brand & Digital, Inbound Marketing, and Corporate Communications, you would complete 4 CSV uploads.
Import CSVis really simple. It requires only two columns,
Import CSVis really powerful. It allows you to use the /Quick Actions to do cool things to your new issues like:
Decide what project structure will be for your set of issues. Specifically,
labelswill be used for the project,
sub-epicswill be used to track the work, and
milestoneswill you use for this work effort.
If these structures do not already exist in GitLab, configure them now.
Raw Title Cells, you will enter the text for the titles of your issues.
Raw Descriptioncells, will be the text of the issue descriptions (NO LABELS or Quick quick_actions)
Descriptioncells will be where you use a formula to create the actual title and description of your issues.
quick actionsto issues, depending on your needs.
|1. In the first cell below the
In this case, I've drafted a title: Market Research - Persona as the title of my first issue.
|2. In the cell Above the
|3. In the first
|In this case the formula that pulls together the two cells is
|4. Now, just write new raw titles, and then copy the formula in the
Descriptioncell. Add ANY quick action commands apply to EVERY issue.
quick actionsfor EVERY ISSUE
/quick actions, go to an existing issue in your project and type the quick action in an issue comment. The autocomplete will help you correctly write the
quick action. Simply copy and paste the quick action from the GitLab comment into your spreadsheet.
Raw Descriptioncell, using Markdown, write the issue description how you want it to appear.
=equals sign and then everything is in quotes so that the spreadsheet treats the entire block of text as a string.
Descriptioncell, write the formula that will bring together the
Raw Descriptionand the common actions and the issue actions In this example, the formula is:
=M3&" "&O$1&" "&Q3&" "&R3&" "&S3&" "&T3`
See this working spreadsheet example.
descriptioncells (including the column headers) and copy the contents.
paste as values. This will eliminate the formulas, but will keep the actual values.
Import Issuesbutton and wait for the magic to happen.
Quick Actioncodes. Then, copy and paste the
quick actionsto your spreadsheet. That way your
quick actionswill not have typos or errors.
issue created date). However, if you list your spreadsheet in the reverse order, then your last issues will be loaded first. That means they will be OLDER, and therefore listed last in GitLab issue lists.