Skip to content

Ideas for Business-Friendly GitLab / Project Management Optimizations

Document to discuss with Eric Brinkman (to be broken out and documented in issues).

👯 Cloning epics and related issues

Being realistic, I know that this would be a large scope and so I've included sub-sections below with (in this request's absence) would be a step in the right direction.

Link to issue with details >>

Related request: Epic templates

Issue to be added here >>

If we can’t clone epics and related issues, then the next best thing that could save a fraction of time (i.e. Step 2) would be to have epic templates.

Upon convo with Eric: or fix issue-to-epic promotion issues, and first discuss with FMMs to make sure this doesn't create other problems.

Related request: Epics can't be confidential (This exists now!)

Because we can't make epics confidential, we have to create issues just to house sensitive information, which is inefficient.

Epic assignees

Related request: Issue titles within issue templates

Issue here >>

I’m curious why in a template you can’t specify an issue title. This could save time since I would only need to drop in the name of the event, instead of typing out the title for all supporting issues.

🗓 Calendar functionality that allows filtering by assignee, due date, status, etc.

Issue here >>>

We have due date, but I don’t have a way to see when events are taking place. Would love to see my issues planned out by the date things are taking place, but more specifically see the things that are due by different people in a timeline view.

Would love to see something akin to tasks within issues that can be moved around and assigned to different team members with due dates. The checkboxes get out of hand, and I have to click into and scroll through the issue to find what I need and who I need it from and when.

📝 Planning template - can you recreate my google doc in-product somehow?

This isn't really a priority, but I think it would be cool. I have a googledoc that spits out timelines with formulas to help me plan out when thing should be done based on SLAs.

GoogleDoc

If we want other marketing teams to use GitLab as we do in the future, this would be an enticing feature. To allow the team to set their "SLA Guide" then drop in delivery date and have everything complete for them based on business days.

🥫 Canned responses in issue comments

Issue here >>

Similar to gmail functionality, if you’re typing out similar reminders or requests frequently, this could really cut down on time! I continually ping FMMs with the following messages:

  • @name just a reminder to have this copy to me by tomorrow!”
  • “Test email sent to @name (screenshot below).”
  • @name confirming that the email is set to send out tomorrow at 6 am recipient’s timezone”
  • @name confirming that the email has been sent. Next email copy due by [date]”
  • @name confirming that the email has been sent. Next up is the reminder to go out [date]”
  • @name confirming that the email has been sent. Closing out!”
Edited by Jackie Gragnola