Jump to content

Integration with Drupal Support Ticketing System module


wvd_vegt

Recommended Posts

Hi,

Attached is a first version of a pet project, integration with the Drupal Support Ticketing System module. It has a module for Drupal 7 and off-course the extension dll needed by the PlasticSCM client to communicate with.

It simply adds a module to drupal that implements a xml-rpc service based on Drupal's built-in code. Unzip support_plasticscm.zip in the /sites/all/modules directory of your Drupal server and enable it.

The DrupalSupportExtension.dll (sorry, Windows only) in the VS2020/C# project (PlasticBugTrackerExtension.zip) should be placed a directory support under the extensions directory found at the location of the client (plastic.exe). The archive PlasticBugTrackerExtension.zip also contains the sources (based on both the code supplied here and in the bugzilla integration example).

Configuration is simple, in the PalsticSCM client Preference Dialog, select Issue Tracking and there bind to the Drupal Support Module. As server Url just enter the url to your Drupal server running the Support Ticketing System module, so http://<servername> is the url to enter.

Adding a ticket to a branch in the client is simply a matter of entering the prefix (scm by default) followed by the Drupal node id (you can see that if you hover on a edit link of ticket in drupal).

Note: there is no security implemented yet (did not find a way to enforce it on xmlrpc calls), so you may need to restrict access to the xmlrpc.php file in the webserver.

Note: the open issue in browser button of the client expects drupal to be running in clean url mode.

regards

support_plasticscm.zip

PlasticBugTrackerExtension.zip

Link to comment
Share on other sites

Hi,

Here some screenshot (and a tiny problem in the Client's GUI).

Screenshots 1 and 2 are of the PlasticSCM client. In Screenshot 1 the problem is that a multi-line description is not completly visible in the grid view.

Screenshot 3 is the same ticket but viewed in Drupal after clicking the 'Open issue in Browser' button.

I also could not find a way to display more than one issue in the grid.

Finally the grid is not cleared if changeset is selected without a issue attached (to clear it click the lane between the changesets).

regards

post-1713-0-63481200-1356950964_thumb.jpg

post-1713-0-27120800-1356950981_thumb.jpg

post-1713-0-41149200-1356950988_thumb.jpg

Link to comment
Share on other sites

Wow! Thanks! It's amazing!

Let us test it and we'll take a look into the grid issue.

Do you mind if we publish your plugin in the Labs section, obviously, referencing your name.

Would you be interested in writing a small blogpost explaining the features and some bullet points about the development?

Thanks again!

Link to comment
Share on other sites

Hi Manu,

Feel free to publish it (or i would not have uploaded it). Let me know if you need the url to my Drupal Support bugtracker for testing (I can e-mail/pm the url).

Do you have a format for this kind of blogposts?

Btw the same applies to the vss importer I mailed.

Regards

Link to comment
Share on other sites

Hi

Should have know it was already tried ;-(.

I however has slightly modified code as for the status. 'M' in plasticscm is moved and i expanded it to a delete and an add (instead of just modified) and replaced only 'C' by 'M'. I will make a litte GUI that parses the list of repositories/workspaces so you can make an easy choice.

regards

Link to comment
Share on other sites

I however has slightly modified code as for the status. 'M' in plasticscm is moved and i expanded it to a delete and an add (instead of just modified) and replaced only 'C' by 'M'. I will make a litte GUI that parses the list of repositories/workspaces so you can make an easy choice.

Cooooooooooool

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...