I'm using DOORS 9.6.1.10.  I have a new System Subsystem Specification in a DOORS module and some of the requirements are not being displayed in the correct (Object Number) order.  The order I expect is this:

3.2 (Heading)
3.2.1 (Heading)
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement

The order I get is this, with the 3.2.1 requirements listed after the 3.2.1.2 requirements:
3.2 (Heading)
3.2.1 (Heading)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)

This behavior is not consistent through the module.  Some requirements are listed under the correct heading.

The 3.2.1 requirements were a csv import from Excel.  If I add a new requirement under 3.2.1 in DOORS it is placed with the others, after the 3.2.1.2 requirements.

How do I get the module to sort in the correct order?  Object Number is not an option in the Tools->Sort... dialog.

Thanks for any help.

------------------------------
Bill Reinhold
------------------------------

#Sustainability
#Engineering

Hi Bill,
Are you still having a problem? Is this the order even in the Standard View?  If the Standard View is correct, then there is probably some other sort or filter in the view with the problem; check carefully.
If you still have any problem, can you provide a screenshot?


------------------------------
Joseph Dress
------------------------------

Original Message:
Sent: Tue January 14, 2020 11:46 AM
From: Bill Reinhold
Subject: DOORS Sorting Problem

I'm using DOORS 9.6.1.10.  I have a new System Subsystem Specification in a DOORS module and some of the requirements are not being displayed in the correct (Object Number) order.  The order I expect is this:

3.2 (Heading)
3.2.1 (Heading)
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement

The order I get is this, with the 3.2.1 requirements listed after the 3.2.1.2 requirements:
3.2 (Heading)
3.2.1 (Heading)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)

This behavior is not consistent through the module.  Some requirements are listed under the correct heading.

The 3.2.1 requirements were a csv import from Excel.  If I add a new requirement under 3.2.1 in DOORS it is placed with the others, after the 3.2.1.2 requirements.

How do I get the module to sort in the correct order?  Object Number is not an option in the Tools->Sort... dialog.

Thanks for any help.

------------------------------
Bill Reinhold
------------------------------

#Sustainability
#Engineering

Hi Joseph,

Thanks for the reply.  Yes, I'm still having the problem and it's simple to replicate:

1.  Create a new formal module using the System Subsystem Specification template
2. Add new objects as paragraphs 3.2.1.1 and 3.2.1.2
3. Create a new "Import-Export" view with the following columns:
1. Object Identifier
2. Object Number
3. Object Heading
4. Object Text
4. Save the module and export to Excel
5. In Excel, add new "requirements" rows under 3.2, 3.2.1, 3.2.1.1, and 3.2.1.2 with only the Object Text column filled in.
6. Save the spreadsheet as a CSV file
7. In DOORS, Import the CSV file.
8. Observe the requirements are out of order in both views. 
9. In the Import-Export view, observe the new requirement objects have been assigned the expected Object numbers

------------------------------
Bill Reinhold
------------------------------

Original Message:
Sent: Tue January 21, 2020 04:23 PM
From: Joseph Dress
Subject: DOORS Sorting Problem

Hi Bill,
Are you still having a problem? Is this the order even in the Standard View?  If the Standard View is correct, then there is probably some other sort or filter in the view with the problem; check carefully.
If you still have any problem, can you provide a screenshot?


------------------------------
Joseph Dress

Original Message:
Sent: Tue January 14, 2020 11:46 AM
From: Bill Reinhold
Subject: DOORS Sorting Problem

I'm using DOORS 9.6.1.10.  I have a new System Subsystem Specification in a DOORS module and some of the requirements are not being displayed in the correct (Object Number) order.  The order I expect is this:

3.2 (Heading)
3.2.1 (Heading)
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement

The order I get is this, with the 3.2.1 requirements listed after the 3.2.1.2 requirements:
3.2 (Heading)
3.2.1 (Heading)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)

This behavior is not consistent through the module.  Some requirements are listed under the correct heading.

The 3.2.1 requirements were a csv import from Excel.  If I add a new requirement under 3.2.1 in DOORS it is placed with the others, after the 3.2.1.2 requirements.

How do I get the module to sort in the correct order?  Object Number is not an option in the Tools->Sort... dialog.

Thanks for any help.

------------------------------
Bill Reinhold
------------------------------

#Engineering
#Sustainability

I've found a kludgy workaround for this:

1. Insert a dummy 3.2.1 heading object
2. Cut the 3.2-x requirements and paste them to the dummy 3.2.1 heading.  They now get 3.2.1-x Object Numbers.
3. Delete the 3.2.1 dummy heading object.  Those requirements now get 3.2.0-x Object Numbers and they stay where they're supposed to be.

------------------------------
Bill Reinhold
------------------------------

Original Message:
Sent: Wed January 22, 2020 04:35 PM
From: Bill Reinhold
Subject: DOORS Sorting Problem

Hi Joseph,

Thanks for the reply.  Yes, I'm still having the problem and it's simple to replicate:

1.  Create a new formal module using the System Subsystem Specification template
2. Add new objects as paragraphs 3.2.1.1 and 3.2.1.2
3. Create a new "Import-Export" view with the following columns:
1. Object Identifier
2. Object Number
3. Object Heading
4. Object Text
4. Save the module and export to Excel
5. In Excel, add new "requirements" rows under 3.2, 3.2.1, 3.2.1.1, and 3.2.1.2 with only the Object Text column filled in.
6. Save the spreadsheet as a CSV file
7. In DOORS, Import the CSV file.
8. Observe the requirements are out of order in both views. 
9. In the Import-Export view, observe the new requirement objects have been assigned the expected Object numbers

------------------------------
Bill Reinhold

Original Message:
Sent: Tue January 21, 2020 04:23 PM
From: Joseph Dress
Subject: DOORS Sorting Problem

Hi Bill,
Are you still having a problem? Is this the order even in the Standard View?  If the Standard View is correct, then there is probably some other sort or filter in the view with the problem; check carefully.
If you still have any problem, can you provide a screenshot?


------------------------------
Joseph Dress

Original Message:
Sent: Tue January 14, 2020 11:46 AM
From: Bill Reinhold
Subject: DOORS Sorting Problem

I'm using DOORS 9.6.1.10.  I have a new System Subsystem Specification in a DOORS module and some of the requirements are not being displayed in the correct (Object Number) order.  The order I expect is this:

3.2 (Heading)
3.2.1 (Heading)
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement

The order I get is this, with the 3.2.1 requirements listed after the 3.2.1.2 requirements:
3.2 (Heading)
3.2.1 (Heading)
3.2.1.1 (Heading)
3.2.1.1-1 (Requirement)
3.2.1.2 (Heading)
3.2.1.2-1 Requirement
3.2.1-1 (Requirement)
3.2.1-2 (Requirement)

This behavior is not consistent through the module.  Some requirements are listed under the correct heading.

The 3.2.1 requirements were a csv import from Excel.  If I add a new requirement under 3.2.1 in DOORS it is placed with the others, after the 3.2.1.2 requirements.

How do I get the module to sort in the correct order?  Object Number is not an option in the Tools->Sort... dialog.

Thanks for any help.

------------------------------
Bill Reinhold
------------------------------

#Sustainability
#Engineering