I suggest you ...

Expose an issue ID

Provide a way to track an issue using a unique ID. This would allow reference outside of Teamwork.

28 votes
Vote 0 votes Vote Vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    I agree to the terms of service

    You'll receive a confirmation email with a link to create a password (optional).

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    anonymousanonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      I agree to the terms of service

      You'll receive a confirmation email with a link to create a password (optional).

      Signed in as (Sign out)
      Submitting...
      • LukasLukas commented  ·   ·  Flag as inappropriate

        In addition to a visible unique ID I find it very helpful and timesaving if I can navigate from an issue to subversion per ID. Of course the ID has to be in the commit-statement with a defined prefix/syntax so it can be recognized. The issue-tracker "trac" does this very well (it defines #123 as issue-ID and [123] as changeset-ID). It would be great to see this in teamwork. This functionality brings together what belongs together - an issue-ticket and the changes in code.

      Knowledge Base and Helpdesk