Jump to content
crychair

Plastic issue tracking missing on Linux

Recommended Posts

Hello,

 

I am currently trying to setup JIRA and got to my next step of integrating with plastic. We use Linux machines for development and when I went to go set up the preferences for issues tracking I noticed that they dont seem to exist the same way as the windows client. I have 5.4.16.689 currently. And i do see there was an update recently, but I did not expect that to add this functionality. 

 

Is there a way to set up issue tracking on this version of the linux client?

 

Should I just downgrade back to an older version of the linux client?

 

Thanks for the help,

 

Evan

Share this post


Link to post
Share on other sites

I have tried setting up the config files(cleint.conf and jiraextensions.conf) and moving the jiraextention.dll to the client folder, but I haven't gotten any indication that it even seeing these files.

Share this post


Link to post
Share on other sites

Hi, please follow the next steps:

 

Files to configure:

${HOME}/.plastic4/issuetrackers/<server>/allrepos/<issuetracker>.conf
${HOME}/.plastic4/client.conf

Example of client.conf extra lines:
<Extensions>
<Extension AssemblyFile="C:\Users\Miguel\wkspaces\codice-wrk\01nerva\bin\client\extensions\jira\jiraextension.dll" />
</Extensions>

The issue tracker .conf files can be generated on windows and then transferred to the target linux machine.

Share this post


Link to post
Share on other sites

Linux

no issue trackers folder exists?? Placted config in the .plastic4 folder for now and this did not work

Edited the client.conf

Just want to reiterate that im on the gtk version of plastic.

 

What is the "<server>" syntax/name?

 

I tried making the folder structure 

issurtracjers/jira/allrepos/jira.conf

I do not get nay errors it just seems like plastic is not recognizing what I want to do.

Share this post


Link to post
Share on other sites

Looked on the windows machine and copied the <server> folder used there. It did not seem to make a difference. This folder structure was no installed for the gtkplastic version I am using on linux and leads me to believe the functionality was never added to the new gtk version. Is this true?

 

If not i can't seem to get any indication that it does exist.

 

Thanks for the help though, I am just hoping to use this software together.

Share this post


Link to post
Share on other sites

Hi,

 

We have tested the gtkplastic - Jira integration. But as I´ve said it´s not very user friendly now. We are adding more and more features each new release (and a full issue tracker GUI support will be included as well).

 

Meantime, please review that your "${HOME}/.plastic4/issuetrackers/<server>/allrepos/jira.conf" is configured for "Task per Branch" and the rest of the values are correct as well. The checkin results will be logged into the issue tracker linked task. 

As you probably know, the branches and the JIRA tasks are linked by the "Branch prefix" value of the "jira.conf".  You could even configure the JIRA integration in a Windows machine, check that everything is properly working and then just copy the "issuetrackers" folder in your Linux machine.

 

You could attach the gtkplastic log to check why the integration is not properly working in your scenario.

 

Regards,

Carlos.

Share this post


Link to post
Share on other sites

So if this all works I should be able to create a child branch from a task right? And that would show up as an option in the linux GUI?

 

Or is this more limited functionality at this point where is will only fill in the custom field.

Share this post


Link to post
Share on other sites

Sorry, I´m afraid that it´s still a limited functionality. Only the checkin comments will be logged in the linked issue tracker task.

 

Regards,

carlos.

Share this post


Link to post
Share on other sites

Yes, Actually it was the default behavior also in the Windows GUI until a few months ago where we allowed to link and select the tasks during the branch creation including a new menu.

 

Regards,

Carlos.

Share this post


Link to post
Share on other sites

Thanks for the help, moving the folder from windows directly to linux worked fine. I would suggest adding the file structure and configuration files to you administration guide.

Share this post


Link to post
Share on other sites

OR. One the windows one could you have it empty and fill the plasticSCM field in JIRA when an issue is added to a changeset. Because currently the only way to get that field filled in is to checkin against it. Which I cant do because we develop on linux. 

Share this post


Link to post
Share on other sites

When linking JIRA Issues to changesets nothing is updated in JIRA to reflect the change. When checking in items against an issue it updates the Plastic SCM field in JIRA.

Could it be an added setting that the info that would normally only be updated when checking in against an issue be updated when just linking an issue to a changeset.

This way I could add issue to changesets after checking in and keep JIRA updated with more information.

Share this post


Link to post
Share on other sites

any news on this? I'm tryint to develop my ownb extension for plastic and favro and I don't find a gui like windows, or any way to install it to test it.

I'm using latest plastic6 from repos installed today.

Share this post


Link to post
Share on other sites

Hi Ignotion,

I'm sorry but it's not supported yet, we don't have plans to have it soon as it's not having enough priority yet.

But just for you to know you can manually configure it as it's explained above, I know it's a manual process (2 steps) but it should work.

Share this post


Link to post
Share on other sites

Could you explain how to match branches to tasks manually. If I set up the Task by Branch files and then want to tag it all.

 

The main problem I see is that JIRA is only updated on checkins not when branches are tagged. So tagging after the fact doesnt get you anything.

Share this post


Link to post
Share on other sites

Hi crychair,

Our JIRA extension doesn't make JIRA display any information regarding the Plastic SCM branch linked to each particular task at the moment. Besides the information stored after each checkin, that is. The 'Task on branch' working mode applies only to how the Plastic SCM client displays task information in its views.

The JIRA extension (or any other Plastic SCM issue tracker extension) only works as an adapter to retrieve information from the issue tracker so it can be displayed on the Plastic SCM client, and additionally perform some actions using the issue tracker remote API.

 

If you'd like to see your workflow implemented in our extension system you can propose it in our UserVoice website and see if it gets enough traction! https://plasticscm.uservoice.com/forums/15467-general

 

Regards,

Miguel

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×