Menu

#169 Assigned CR numbering does not consider all tabs

None
new
None
Registrar
major
defect
2014-03-05
2014-03-05
No

The currently assigned CR numbering only considers the first tab (typically the Current tab). This means that when a CR block is created and uses the last numbered CR (moved to a secondary tab), then newer CRs will not be numbering correctly. The workaround is to temporarily create a false record in the CR Status file at the bottom of the Current tab, add the new CRs, then delete the temporary false record. The recommended approach is to search the other tabs for the latest CR number AND/OR to provide the user with an entry to specify the CR number (override).

Discussion


Log in to post a comment.

MongoDB Logo MongoDB