Problem when clicking on linked item in svn commit message

stroebti
Posts: 10
Joined: Fri Oct 13, 2006 12:48 pm

Problem when clicking on linked item in svn commit message

Postby stroebti » Fri Nov 03, 2006 2:12 pm

FastTrack has this great feature that you can click on a workitem that has been referenced by it ID in the svn commit message.

Anyhow I had some problems as FastTrack tells me that the item is not available although I have checked out the project from polarion server.

Link works inside polarion webinterface (item to code)

Now in Eclipse:
when I check in subversive the commit log I can see the item id clickable. When I click on it however I get the message that the item is not available (checked out)

Anything I have to take care when checking out projects from polarion server ???? Help is greatly appreciated :?:

stroebti
Posts: 10
Joined: Fri Oct 13, 2006 12:48 pm

Additional Comment: FastTrack uses folder as additional info

Postby stroebti » Fri Nov 03, 2006 2:41 pm

In polarion I can link a workitem only by specifying the item id.
In FastTrack also the folder in Subversion is referenced

Product_A/PRODUCT_A-19 (example of Fasttrack link to workitem)

Therfor I think my polarion links do not work..any ideas what I could do ?

JiriWalek
Posts: 49
Joined: Fri May 05, 2006 3:05 pm

Re: Additional Comment: FastTrack uses folder as additional

Postby JiriWalek » Tue Nov 07, 2006 6:44 pm

Hi Tim,
can you please:

* copy here the exact commit message from log
* how do you link workitems? by writing id or using table to select WI in commit office. Only second should always work well.
* tell us what is your project id in polarion
* tell us what is the eclipse project name where the tracker is stored

Thanks,
Jiri Walek
jiri.walek@polarion.com
Polarion Software

stroebti
Posts: 10
Joined: Fri Oct 13, 2006 12:48 pm

More information on Commit Message

Postby stroebti » Tue Nov 07, 2006 7:53 pm

Project was created in Polarion
SVN_Path:
products/Product_A/.polarion
products/Product_A/trunk
products/Product_A/tags
products/Product_A/branches
products/Product_A/branches/test


In polarion project id:Product_A
I have workitem PRODUCT_A-16

Now I create a file (test.txt)below
products/Product_A/branches/test
and commit it via tortoise (add+commit)

As commit message I enter:
PRODUCT_A-30

revision number is automatically linked inside polarion web interface.
Revision number is clickable.

Now I checkout same project into eclipse: (find projects to checkout)
Project id in eclipse is now Product_A.tracker (this may be the problem...)

Now if select log history of file test.txt in FastTrack.
Now I click on PRODUCT_A-30 =>

Here I am again ;-)

JiriWalek
Posts: 49
Joined: Fri May 05, 2006 3:05 pm

Re: More information on Commit Message

Postby JiriWalek » Wed Nov 08, 2006 11:41 am

As already mentioned here: http://forums.polarion.org/viewtopic.php?t=603
the links should be in format Product_A/PRODUCT_A-30

(the first is project id, the second is project prefix = not unique)

But you should use "commit dialog > link workitems tab" to link your workitems (not write the id by hand).

To work well with your Product_A in your eclipse you should:

* call find projects over Product_A folder
* this would checkout tracker and polarion server project\
* and the trunk folder if it contains eclipse project.

As I understand you right, you have already tracker projects in your eclipse.

Now please try to call "checkout as" over "trunk" folder as let's say "Product_A.trunk" or whatever you want to call it. Change any file in it and commit it do the repository using eclipse (Team | Commit). The commit dialog with "Link workitem" tabs should be opened and you can select the linked workitems in table.

The FastTrack is component to eclipse ide, id does not make much sence to use fasttrack to track your workitems and use tortoise to work with svn. You should use subversive svn client in eclipse to colaborate with svn/

More Info if you are interested

Generally there are two layouts supported:
* Product_B
** .polarion (containes tracker)
** trunk
*** trunk is the eclipse project so it contains .project, and the eclipse project is called Produce_B
** branches
*** branch_a
**** copy of trunk

than after find project you would have following projects in your WS
* Produce_B (trunk)
* Product_B.tracker (.polarion)
* DOMAIN.polarion (polarion server configuration = .polarion in repo root)

Or you can have multiple eclipse projects in trunk
* trunk
** Product_B.UI
** Product_B.Core

Than you would have after find projects
* Produce_B.UI
* Produce_B.Core
* Product_B.tracker (.polarion)
* DOMAIN.polarion (polarion server configuration = .polarion in repo root)
Jiri Walek

jiri.walek@polarion.com

Polarion Software

stroebti
Posts: 10
Joined: Fri Oct 13, 2006 12:48 pm

Tortoise commits should be supported as well

Postby stroebti » Thu Nov 09, 2006 6:15 pm

As I understand this correctly tortoise commits are not clickable. I can understand the behavior as intended.

Anyhow I would see it as an enhancement as you can't expect all people in a project using the same IDE.

Lets close thread here...
Thanks for your help

JiriWalek
Posts: 49
Joined: Fri May 05, 2006 3:05 pm

Re: Tortoise commits should be supported as well

Postby JiriWalek » Thu Nov 09, 2006 6:22 pm

Not exactly, if you use the Project prefix when using tortoise commit dialog then it works.

Eg: FastTrack/PLC-A1HGZ

Simple FT needs the project id to be part of workitem id.
(you could feel it reduntant cause your project prefix = projectid).
Jiri Walek

jiri.walek@polarion.com

Polarion Software

stroebti
Posts: 10
Joined: Fri Oct 13, 2006 12:48 pm

Thanks for this additional ifo

Postby stroebti » Fri Nov 10, 2006 1:37 pm

Hi Jiri,
thanks for this additional useful Info.

Anyhow...I don't I don't understand why an ID of an workitem is not enough.
WorkitemIDs should be unique (thats the idea of an ID I guess)

Is it because you may have multiple repositories and some item ids may be duplicate. ?

Best
Tim

JiriWalek
Posts: 49
Joined: Fri May 05, 2006 3:05 pm

Re: Thanks for this additional ifo

Postby JiriWalek » Mon Nov 13, 2006 9:15 am

stroebti wrote:I don't I don't understand why an ID of an workitem is not enough.
WorkitemIDs should be unique (thats the idea of an ID I guess)


No Tim , you are wrong, the WI ids are unique only in the scope of project. The only perfectly unique identification is ProjectID/WI-id

On the other hand FT could handle that better and if there is WI id without project id, it could make a try to find it and if there is just single wi , than open it, otherwise open dialog to select the one.
Jiri Walek

jiri.walek@polarion.com

Polarion Software


Return to “FastTrack - Tracking deeply integrated in Eclipse IDE”

Who is online

Users browsing this forum: No registered users and 1 guest