Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4275

Closed
Open
Created Jun 11, 2013 by Administrator@rootOwner

Issue-Number-cycle per project

Created by: lippoliv

Hey there. Currently there is an global issue-number-cycle.

You have two empty Projects. You create an Issue to Project 1, its Isse 1. You create an Issue to Project 2, its Issue 2.

This is'nt the way it works on github.com and it isn't actually an "cool" way.

I know: It's a lilttle thing, but it will be pretty nice, if this Numbering won't be global, better it should be per project.

If I have several Users, they will be wondering, if their second Issue don't got the number 2, or also why their first Issue don't got the number 1... you know?

Assignee
Assign to
Time tracking