#1918 No longer have unique ticket numbers within a project

self-service
Chris Tsai
None
2012-12-26
2012-12-09
Bill Wohler
No

I've discovered that bugs, feature requests, and patches all have their own namespace in the new system. This means that a ticket number is not unique within a project.

This brings up a dilemma for us. We used to refer to our tickets as SF #123, but now we can't do that any more. We now have to say something like SF bugs/123. While we debate what new convention to use, I wanted to ask you if there was a way to provide unique ticket numbers across the different tools within a project. That would give us the option of sticking with our existing convention.

Discussion

  • Chris Tsai
    Chris Tsai
    2012-12-10

    It's not possible to have unique numbers across tools, but the alternative, we'll follow-up with on [#1922].

    As for a a naming convention, I would actually recommend something like, [feature-requests:#10], or even [mh-e:bugs:#269], since that will utilize the Artifact linking feature on our site, and will create links to the ticket itself if it's used in a Markdown processed part of the project (eg., tickets, forums, commit messages, etc., however, not mailing list archives, at least not yet).

    Does this help?

    Regards,
    Chris Tsai, SourceForge.net Support

     

    Related

    Feature Requests: #10
    Site Support: #1922
    MH-E: Tickets: #269

  • Chris Tsai
    Chris Tsai
    2012-12-10

    • status: unread --> pending
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2012-12-26

    • status: pending --> self-service