Some things about P-ALM that need to be improved

Description
phil
Posts: 4
Joined: Tue Oct 19, 2010 9:22 am

Some things about P-ALM that need to be improved

Postby phil » Tue Oct 19, 2010 1:54 pm

After working two weeks with Polarion ALM Enterprise (Build: 3.4.1.20100126-0441) i found quite a few things that could be improved for making things easier.

Below is a little list that coul be easily changed (items not in particular order):

- the wiki-syntax is incomplete (e.g. textindention is only possible with "<blockquote>" but not with ":")
- if you change your view from "edit" to "preview" or from "wiki markup" to "rich text" or any other combination while editing a module the cursor jumps to the beginning of the document which makes it hard to edit larger modules
- some basic windows shortcuts like ctrl-s are not supported
- the shortcuts for the creatin of hierarchical work-items in designer-view are bad since ctrl-right(left) is commonly used to move the cursor at the end of a string while in edit mode
- many many grammar and spelling mistakes in the manual
- no wiki markup in work-item description field editing
- rich text has no possibility to change text color ( since you can copy colored text in the polarion fields the rich text mode is capable of it ) and no possibility to change text size
- rich text editing has no possibility of creating sup and sub text
- in module edit mode (rich text[using firefox]): if you change the size of an table the table is broken. you need to switch back to wiki markup to complete that table (not possible in work-item edit)
- listings created in inside tables are broken if you switch back and forth between rich text and wiki markup
- while working with ie 6 in rich mode: unfrequently a created table is placed outside the polarion frame (relogin needed)
- if you have many modules where you maybe want to use the same images you need to upload it for every module you want to use it (no reuse possible)
- discard changes message even if there are no changes

Since the time i work with Polarion is relativly short i know that maybe some of those things are wrong but please tell me how to do things right then.

Kind regards
phil
Last edited by phil on Wed Nov 10, 2010 2:24 pm, edited 1 time in total.

robertneher
Posts: 47
Joined: Sat Jan 22, 2005 10:56 am
Location: Stuttgart
Contact:

Re: Some things about P-ALM that needs to be improved

Postby robertneher » Sat Oct 23, 2010 6:32 am

Hi Phil,

- the wiki-syntax is incomplete (e.g. textindention is only possible with "<blockquote>" but not with ":")
--> We modified the syntax for XWiki slightly.

- if you change your view from "edit" to "preview" or from "wiki markup" to "rich text" or any other combination while editing a module the cursor jumps to the beginning of the document which makes it hard to edit larger modules
--> Agree. This is an issue we are tracking already.

- some basic windows shortcuts like ctrl-s are not supported
--> Such things overlap with Browser shortcuts and other things. We are trying to find compromises.

- the shortcuts for the creatin of hierarchical work-items in designer-view are bad since ctrl-right(left) is commonly used to move the cursor at the end of a string while in edit mode
--> Will be changed entirely in upcoming version. Please apply for beta on our home page.

- many many grammar and spelling mistakes in the manual
--> Please post. We will improve.

- no wiki markup in work-item description field editing
--> Agree. This is a victim of continuous product evolution. Your idea to have Wiki overall is already in our pipeline for product improvement.

- rich text has no possibility to change text color ( since you can copy colored text in the polarion fields the rich text mode is capable of it ) and no possibility to change text size
--> Oops. We provide text coloring in RTF fields. I will check. Support will post here.

- rich text editing has no possibility of creating sup and sub text
--> Same here.

- in module edit mode (rich text[using firefox]): if you change the size of an table the table is broken. you need to switch back to wiki markup to complete that table (not possible in work-item edit)
--> Same here

- listings created in inside tables are broken if you switch back and forth between rich text and wiki markup
--> This is a bug.

- while working with ie 6 in rich mode: unfrequently a created table is placed outside the polarion frame (relogin needed)
--> This is a bug.

- if you have many modules where you maybe want to use the same images you need to upload it for every module you want to use it (no reuse possible)
--> Please clarify. You like to add same image to every requirement in module?

- discard changes message even if there are no changes
--> Agree. Disappears in next release.

Support may answer as well...

Best Regards,
Robert
Robert Neher, Polarion Software GmbH

NickEntin
Posts: 472
Joined: Tue Oct 24, 2006 10:27 am
Location: Polarion Software GmbH, Stuttgart
Contact:

Re: Some things about P-ALM that needs to be improved

Postby NickEntin » Mon Oct 25, 2010 7:01 am

Dear Phil,

while some things are still not implemented and some are being implemented in the upcomming release, I see you already caught couple things, which were already fixed.
For example,
the shortcuts for the creatin of hierarchical work-items in designer-view are bad since ctrl-right(left) is commonly used


This has been fixed in 3.4.2 version, and we had even yet another bug-fix release later (3.4.3). I'm pretty sure that some of other issues have been fixed in meantime too.

Best regards,
Nick

ChernikovaEkaterina
Posts: 15
Joined: Mon Dec 07, 2009 9:08 pm

Re: Some things about P-ALM that needs to be improved

Postby ChernikovaEkaterina » Mon Oct 25, 2010 7:54 pm

Hi Phil,

- rich text has no possibility to change text color ( since you can copy colored text in the polarion fields the rich text mode is capable of it )

You can change text color, for example, in description via button "Text color".
Just select the text which you would like to change and choose the color.
If you mean some other rich text editors please let me know which exactly.

- rich text editing has no possibility of creating sup and sub text

Our rich text editor supports sup and sub tags (it means that you can copy\paste text which uses some of them) but can be created just directly in xml file

- in module edit mode, if you change the size of an table the table is broken.

Could you please send us the concrete example of this table (what exactly do you have in edit mode? is it Design page or Home page of module )?

Best Regards,
Ekaterina Chernikova
Polarion Support Team


Return to “Polarion Application Lifecycle Management (ALM)”

Who is online

Users browsing this forum: No registered users and 7 guests