cosmoSys » Issues

In Administration, settings, authentication:

When creating a new project, Bug, Feature and Support are active, but csInfo and csRefDoc do not, and should.

This should be unchecked

Should be something like:

chapnums:

  visible: true

  selectable: false

  label: Chapters

csOldCode:

  visible: true

  label: Ext. code

status:

  visible: true

  label: Status

assigned:

  visible: true

  label: Assigned to

For instance, the Manager can not see the MainReport!

The word issue or the word requirement are too much focused.

The translation should be Item, which is more general.

Other option is element, which is more far from tasks, but closer to modelling.

The word "requirements" shall not be appended to the title anymore.

When we export a Test plan, we are seeing the word requirements.

The Developer role does not see the MainReport tab, but s/he can view the MainReport navigating through the cosmoSys tab.

They have to be shown as tasks, this is a regression.

See https://otro.csys.corujadigital.tech/issues/4

Currently, the csInfo and csRefDoc custom fields have no workflow. You can set csID, for instance. This has to be solved in the migration, same it was solved when creating the rq items.

The user should be able to declare a project to belong to a "type" or "document type". These are some samples:

• Issue tracking.

• Requirements.

• Test plan.

• Test run.

• PORIS model.

• Arquitecture.

With this setting, it would be easy to achieve accurated document titles, see #14 for reference.

We will be able to select the appropiate default template for exporting, taking it from cosmoSys, cosmoSys-Req, or cosmoSys-Req-PORIS assets.

The treeview using key is not working because the check_if_login_required function refuses the access based in keys, and then the user is anonymous.

This has to be fixed in order to allow setting the instance as "login required"

Changing it to rqMnaager solves it in csys.cosmobots.eu. Check if this is systemathic and if the Developer has the same problem.

MainReport is a cosmoSys feature, not a cosmoSys-Req one.

The settings are not set at the beginning, so the format is A4 Landscape while the Settings form shows A4 Portrait.

A migration should be executed.

We should check the permssion system to know why a freshly installed Easy X plugin set is not correctly seen by users which are not admin.

We have a concept for an item (requirement) being a clone of another one, so one is the master (writable) and the other is the slave (read only), so we can have an internal requirements document and create other documents for suppliers, with the same requirements, so they can read the requirements without having access to the internal document.

We shall extend this feature to projects. We need a script to generate a clone of a project where all its items are read only clones from the original project's items.

We shall also develop a script to be executed regularly which will delete clone requirements if the master ones are deleted.

See #45 for an introduction.

In some cases the same master document shall be cloned for several institutions. The cloned requirements have some fields which shall not be keep in sync with the master ones, because each of the clones may change their values independenly. For instance, the compliance fields shall not be copied in the clone, as every institution will report their specific progress, which is an information inherent to the institution, not to be feedbacked to the master project, and not to be overwritten everytime the master item changes.

Check https://cgr.csys.cosmobots.eu/cosmosys/ev-nur-2024

Check:

https://cgr.csys.cosmobots.eu/projects/ev-nur-2024

https://cgr.csys.cosmobots.eu/cosmosys/ev-nur-2024/dep_gv.svg

Treeview is allowing unauthorized people to see the issues of subprojects they could not be allowed to see

It is always imposing the numbering to subprojects when committing.

In big projects with lots of images like https://asi.csys.cosmobots.eu/cosmosys/p-asicfg-alo the images are not loading in the first time the report is shown (later they all load) but, even with all of them loaded, the docx report does not include all them.

Error is 503 (Service unavailable)

Should give some message, not crash.

If you have, for instance, a 'rq' which is in 'rqDraft' and change the class to csInfo, it will continue in rqDraft. There will be no option to change it to 'csNone'.

In order to fix this, an admin shall modify the Workflow to allow all the existing states to transition to csNone (maybe there is a better way to fix it).

We shall prevent this to happen by incorporating the fixing changes in the cosmoSys migrations.

Field permissions are opened so when a csInfo is in csNone state, user can change the csID.

If a new issue is created, the csID will be void.

This is fixed by setting the permission to read only.

We should fix this so no action is needed.