make consistent status

[wojosc]

@trustedcomputer I'd like to take up this opportunity to talk about "status" which should probably also be consistent all over elements. At the moment we have on ITM Host Item these

Here are the initial ideas
Implementing = the item is planned to be integrated in the system. Is already created in the database but not yet set up and running
Running = item is integrated in the system and is running fine with no issues/problems
Issue = there is an issue created to which this item is linked to via the ITM Management Table. That issue is in a state that indicates that this host item is effected. The status should be toggled automatically when the issue is closed.
Storage = the Host Item is still part of the landscape but not in active use at the moment.
Obsolet = the host item is not being used anymore but should not be deleted from the system as it is often important to also understand the history of the landscape. The item is maybe scrapped, retired, etc.

@trustedcomputer I'll be happy to hear about what you think about these, if they need to be extended or should be less and how the status might be influences by transactions like the issue Doctype. Thanks

[trustedcomputer]

@wojosc I'd be happy to. As you may have noticed from my PRs, I'm still lacking in my overall understanding of how all the many doctypes are supposed to work together in a real-world workflow. That's why I've tried to limit what I work on to small areas where the function is obvious to me. But I do think I could go through some of the doctypes and look at the different options for "status" that are there and see if they could be made more consistent.

[wojosc]

thank you for your feedback @trustedcomputer let me take this opportunity and create a video on how the app works. I am aware there might be some issues as I test that but I also know about most of those pitfalls and will be able to fix them on the fly.
This video shall then give a good idea of how the app works. From that it is then hopefully easier to move forward. Please bare with me for a week or two to complete this though.

[wojosc]

@trustedcomputer see this video: https://youtu.be/tvmy8EKvgu4

[trustedcomputer]

Thank you, @wojosc I look forward to reviewing the video.

[trustedcomputer]

Thanks so much for the video. It really helped my understanding. Here are my findings and thoughts for status:

Used in:

1. itm_host_item
2. configuration_item
3. licence
4. solution
5. it_backup
6. ip_address
7. itm_user_account
8. itm_software
9. itm_solution
10. it_checklist
11. software_instance
12. user_account
13. subnet

The most common/standard status options are currently:

1. Implementing
2. Running
3. Issue
4. Storage
5. Obsolet

Recommended changes:

1. I believe a status of "planned" may be helpful in the standard status options, for those items not yet implemented
2. "obsolet" should everywhere be changed to "obsolete" to correct for the English spelling. Based on what I've seen so far, I believe the strategy is to standardize on English everywhere in code and translations would be used for localizing in other languages.
3. it_backup could have "Storage" added to the options, for archived storage media for example
4. user_account and itm_user_account could remove "Storage" as an option, I can't think of a scenario where this would make sense
5. itm_software should change from Active and Outdated to the standard options
6. To me, it makes more sense in software_instance for "Uninstalled" to be the final option instead of the first one
7. itm_software_instance should have this field added with the same options as software_instance (it did not get copied from the old doctype)