One of the key strengths of IssueNet is the capability of multiple distinct and even custom issue types to exist in the same database.  Allowing that level of diversity requires several housekeeping functions to keep things organized and easy to find. 

A new feature introduced in IssueNet 5.1, "Sequence Number Inheritance", allows different issue types to pull their unique ID numbers from a common pool.  The default behavior prior to this addition was to assign the ID number based on the issue class, so you could have DEFECT 1, SUPPORT TICKET 1, and OPERATIONS ISSUE 1.  With the new setting these would not share an identical numeral.  For more on this feature and how to best apply it to an existing database, please see our Tech Tip on the subject. 

Sequence Number Inheritance Tech Tip