Polarion Software

a small side remark: with the [relatively] new Live Report, you can compose such traceability view in more visual form (e.g. without much of wiki coding), and don't forget you can use SQL queries for compound statements, if you wish. not as a reference, but just as an example (show all tasks, which ...

Hi,

I'd recommend to address it to support - it's a bit hard to understand from the forum thread, what's going on.

Best regards,
Nick

Hi, more comprehensive answer you can get from support, and I don't remember if there is a configuration options to change color of Heading1 in "hardcoded" PDF export. Through XML Export - you can choose PDF:XML-FO export (Apache XML Formatted objects - you'll find tons of references in in...

Hi, I think we should have somewhere documentation about what to take care during move of Polarion from one server to another. E.g. while repository content is pretty location-agnostic, you should probably preserve host-name of moved server, thus old email notifications or exported reports with hype...

that's actually still a custom field, therefore from traceability point of view it's still there, disregarding of configuration (you can still find by it, see in the history of changes, etc.) I don't remember exactly, but probably if you set a field to empty value, it will be removed from definition...

Hi Christian, Polarion is friendly enough to accept "unknown" (unconfigured) values. I.e. let's say you had an item with "customField:test" and you wanted to change it to "customField:tested". (so far we're speaking about query/persistency, not about display name of the...

Hi, when you connect Polarion to an external repository (which might be e.g. SVN, Git, Perforce or any custom integrated one), Polarion will use those URLs to open: preview of the linked resource/revision or correspondingly, diff of the resource with previous version. Check Administration/Repositori...

Hi, looks like you're looking for this method: http://almdemo.polarion.com/polarion/sdk//doc/javadoc/com/polarion/alm/ws/client/tracker/TrackerWebService.html#getEnumOptionWithEnumId(java.lang.String,%20java.lang.String,%20com.polarion.alm.ws.client.types.tracker.EnumOptionId) TrackerService:: EnumO...

Hi, unfortunately my remark will be - what you described is not clear :-) What database you're speaking about? There is historical database, which keeps all history of all objects (e.g. if you deleted a requirement from actual product, it doesn't mean that this requirement was not implemented in the...

Hi, Assuming that the mentioned kind of variation happens multiple times for different reasons in your master requirements, this represents a good use case for the 150% concept provided in Polarion VARIANTS. A Polarion Feature Model is used to control selection of requirements from master documents ...

Hi Bob, refer to the help of Polarion, e.g. here: http://almdemo.polarion.com/polarion/help/?topic=/com.polarion.xray.doc.user/agchUsersPermissions.html search there for "Configuring the Default User Role(s)" Hope this helps, if not, just approach Polarion Support - they'll assist you to f...

Hi, I'd recommend you to contact support. In the log files you (or they) should be able to recognize what's happened. In worst case (whatever defects) - only information from your browser, i.e. not-yet saved data may be lost. Everything, what was sent to the server is versioned and recoverable. Best...

Hi, I never implemented hook-scripts myself, therefore may only speculate about problems. But couple points you may find useful: - be careful when you parse commit message, e.g. if commit message contains "Fix for BUG-123" - it will be recognized in ALL(!) projects, which have this prefix ...

Hi François, not sure if I understand your issue correctly: - in the self-implemented workflow function you can set all fields (including resolution) as you wish - you just need to program it. - constraint "only field that can be set in an action is the date" is applied only for the out-of...

Hi, if you're using Polarion 2014, you can use the Planning feature (this will replace the old Agile-wiki pages, as more convenient). This allows you to do following: - create a common backlog (let's say it will be Plan "Common backlog") - create subplans Team1, Team2, Team3 (the mapping o...