Caliber Feature Requests
-
WYSIWYG for Description Field and DocFactory
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.
36 votesWe are working on incremental improvements to both the Description field and resulting outputs. Our latest release of Caliber continues to improve on both Author editing and DocFactory formatting consistencies.
-
Persist CaliberRM data in a relational database
Persist CaliberRM data in a relational database
34 votesCaliber 11.4 (12/1/2014) provides an integration with Borland Connect that provides a user-defined sync with the Borland CM Hub. This allows access to the data in a relational database.
-
Allow Caliber Review to open ALM links
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
30 votesThis item is currently under review and has been added to the backlog.
-
Set default font for requirement descriptions and text.
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.
20 votes -
Improve Table functionality with the description field.
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
19 votes -
Ability to output user defined attributes of traced requirements in DocFactory
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.
18 votesThis is a capability that we realize will add great value and it will be considered for future releases.
-
Provide ability to delete projects / data from DB
Provide ability to delete projects / data from CaliberRM database
17 votesContact the Caliber Support team for improved utilities and scripts to assist with maintaining your database.
-
Enable the filtering of Traces using DocFactory syntax
The ability to break out traces based on a pre-defined attribute. For example, let's say I have a user defined attribute set up that captures the type of requirement - use case, business requirement, business rule, functional, non-functional.
Within my project, I have a use case that traces from a Business requirement, and traces to business rules, functional requirements and non- functional requirements. Currently, when I produce a doc factory export using my SRS template, I can only filter on the trace type i.e. Trace From or Trace To. What I would like to be able to do is for…
16 votesThis item is in the backlog but is not on our current roadmap. We recognize the value of this capability and this will be considered as we work on traceability improvements in the product.
-
Table height problems: TheTables do not dynamically resize itself in Caliber
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.
15 votes -
Ability to take Caliber project "offline"
Ability to take Caliber project "offline", make changes and resync with server
15 votesPlease contact the Caliber support team for information on how to download and use the Caliber offline utility. We continue to make improvements based on your feedback.
-
Provide full web based requirements editing
Provide full web based requirements editing
14 votesEditing of Caliber via web will be available in Atlas 1.0 which will be available on 1/7/2014. Existing caliber customers can use this in parallel with their existing Caliber installation. More information will be provided as we get closer to the launch date.
-
Create a formalized review module to track requirements review
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.
12 votes -
can apply the filter to the requirement tree in caliber author
User can apply the filter to requirement tree in caliber author, use can check his interest requirment but still have the hierarchy structure.
10 votesThis capability is available in Atlas 1.0 on 1/7/2014. It will work in tandem with your current Caliber projects and is available to existing Caliber users.
-
Enforce CaliberRM setting so that users have to enter a comment
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.9 votes -
CaliberRDM localization for French
CaliberRDM localization for French
9 votesAfter we complete some more global localization, we will have the ability to localize in French. Still being worked on and still under review.
-
Extend spell checker to cover requirement name and textual user defined attributes.
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.
9 votesIt only makes sense to spell check “everything” that you are working with. This is a feature that will be implemented at some point in the future.
-
Baseline Approval Workflow
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.
9 votesWe are planning workflows for both individual requirements and baselines. This item is in the backlog but has not been formally planned.
-
Caliber review - view requirement versions
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
9 votesCurrently, you have the ability to choose a baseline which will show specific versions that are associated with the baseline, but not at the individual requirement level.
This capability is available in Atlas 1.0 on 1/7/2014. It will work in tandem with your current Caliber projects and is available to existing Caliber users.
-
New Requirement Notifications
It would be nice if you could register at the requirement type level, so that all child requirements are registered to send notifications. Right now, you have to go to every parent requirement under a requirement type and register.
8 votes -
Functionality for branching and merging
Most business units have parallel development projects working on the same product family. Consequently, there is a urgent need for branching and merging, as they already use in software development environments. Branching enables them to make changes on the same requirement without disturbing the other development projects. They also need to generate documents for each branch and create baselines for each branch. At a specific moment in time, there is a need to merge the branches again, where they expect the tools to support them in the process of determining the exact changes and choosing which changes are merged back…
8 votesThis capability will be delivered in our Atlas technology since it is built on top of a Change Management Hub.
This technology is being reviewed and will likely be scheduled for a release late in 2015.
- Don't see your idea?