I need to clarify....... from within the Use Case / Activity / etc. dialog box, I can enter Requirements on the Require tab, which I understand to be internal requirements. The status defaults to 'Proposed' on this dialog page. If I move them to External from this page, the status remains as 'Proposed'.
If I choose to insert a new element (ctrl + M, or right mouse click on the package) and choose the element type to be Requirement, the status in the dialog box defaults to 'Approved' (if it is available in the status list). Other elements default to 'Proposed' (if it is available in the list).
I have deleted all of the status, and re-added two status - Proposed and Approved. With these two status, the above scenario still exists. I then removed the Approved status and added another status - 'NEW'. When I choose to insert a new element (ctrl + M, or right mouse click on the package) and choose the element type to be Requirement, the status in the dialog box defaults to 'blank' - I have to choose the status from the drop down list if I want that field populated.
It appears that there is some code to default to 'Approved' status for requirements if it is in the list.
I have changed the sort order of the status by making the 'Proposed' status '_Proposed' to bring it to the top of the list - that did not work. When I deleted all of the status, I added Proposed first, then Approved, and it still defaulted to Approved, so it does not appear to be related to the order in which the status is entered.
I have not tested all of the elements, but the ones I have played with all default to 'Proposed' (if Proposed is in the status list) with the exception of Requirements.
Therefore, I am lead to believe that either there is (or should be) a place to configure the default value for status, or it is hard coded in the app.