The content of the Description Field in CaliberRM can bee edited as RTF. But the output by the DocFactory to the generated Word-Document does not look allways good. Tables are not the same size, embedded objects are to big. The font depends on how an how edited it the last time. The font and size depends on the personal option settings of the IExplorer.

Persist CaliberRM data in a relational database

If you only have access to Caliber Review and do not have the Caliber Author component installed, you are not able to open ALM links.

Therefore I am asking for Caliber Review to be able to handle ALM links

Would love the ability to set a default font for all requirements in Caliber. Right now, if I cut and paste from Word to Caliber, the font from MS Word is kept. it's annoying when looking between requirements to see many different fonts and font sizes.

The current limitation of the table functionality in the description field, prevents us from utilising this feature fully including features such as resizing, colour shading, alignment and shading.

As this is a HTML table, I believe a good example would be something similar to what Google use for Documents in Google Drive

Currently the DocFactory syntax supports the output of builtin requirement attributes of traced requirements when using the $begin_traces command.

I would like to be able to output user defined attributes of traced requirements inside a $begin_traces command.

Provide ability to delete projects / data from CaliberRM database

Ability to take Caliber project "offline", make changes and resync with server

The tables copied into the requirement description field do not dynamically resize themselves. If a standard 3 row by 3 column tables is copied into a requirement description with text in each cell then if any extra text is added to any cell so that it is longer than the ROW length the table is not dynamically resized. The bottom row is however resized. Can this be developed to ensure the tables copied dynamically resize themselves.

Provide full web based requirements editing

Create a module that you can push a baseline (or set of requirements) to approvers to review requirements. A formalized review where you can track who, when and what requirements and Visualize artifacts were reviewed. Need abiliy to set a deadline date for review, allow for comments. View the total number of requirements for review and the approval states. View the approvers and the approval states for their requirements.

User can apply the filter to requirement tree in caliber author, use can check his interest requirment but still have the hierarchy structure.

It would be very useful if the spell checker could spell check requirement names and text user defined attributes in addition to descriptions.

When I produce requirement specifications using the document factory I have perfectly spelt requirements, but Word immediately highlights all my errors (mostly typos) in the requirement name and in textual UDF fields.

I would be useful if these could be highlighted at the point of entry.

In CaliberRM end users can set many preferences such as whether or not to hide tabs and whether or not to request a comment on saving a requirements.

Is there a way to enforce one or more of these settings so that caliberRM users have to enter a comment?
Or so that preferences can be disabled.

CaliberRDM localization for French

I would like to have a approval workflow for baselines, in a way that only approved baselines would be shown in Caliber Review and those pending approval whould display only to there´s signatories. In addition, rejected baselines would not be shown in Caliber Review. and rejected baselines would have a difrerent icon in Caliber Author. And Caliber Review would always show newest baseline when openning a project.

In the Caliber Review we only can see the last version of a requirement. Is it possible that in new versions it could be possible to select

Web Client – As a system owner, I want the full features/functionality of Caliber RM to be available as a web client and keep me out of the business of client install support and version management.