CVS edit link for MarkFischer

I needed a way to display issues from our JIRA issue tracker inside of Drupal. (http://www.atlassian.com/software/jira/). There were no existing modules that did this that I could find, so I decided to write my own. The module copies issues from JIRA and creates Drupal nodes, one for each issue imported. It is intended as a read-only way to display the current status of JIRA issues. Each time the import runs (via cron) all existing issue nodes in Drupal are deleted, and new nodes are created.

After finishing it, I realized that it would probably be helpful to other people. I posted in the module development ideas group (http://groups.drupal.org/node/58388) asking if anyone had heard of this, or would be interested in it, and have received a lot of interest. After many months of wrangling with my University's office of technology transfer, I finally have the OK to share this under GPL, so here it is!

CommentFileSizeAuthor
#1 jira_issues.tgz3.57 KBMarkFischer

Comments

MarkFischer’s picture

MarkFischer commented
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new jira_issues.tgz3.57 KB

Here's the module!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Needs review » Needs work
Issue tags: +Module review

Hello, and thank you for applying for a CVS account.

As per requirements, the motivation should include more than 2 sentences of module features, and a comparison with the existing solutions.

MarkFischer’s picture

MarkFischer commented

The JIRA Issues module allows for basic importing of JIRA issues into Drupal nodes. The module will fetch all issues from a given JIRA filter, and insert them as nodes into Drupal. As normal Drupal nodes, you can now leverage the full power of Drupal to display, sort, and group these nodes, and present a customized, integrated view for your users. The module creates a new content type - jira_issue. When Drupal's cron runs, all existing jira_issue nodes are deleted, and new ones are added from JIRA.

Fields are mapped from JIRA -> Drupal as follows:

JIRA Field 		Drupal Field
----------		------------
Summary			Title
Description		Body
Created			Date

Additional CCK fields can be mapped to various JIRA fields by customizing a hook function. Examples of several potential mappings are given.

MarkFischer’s picture

MarkFischer commented

comparison with the existing solutions

It looks like there is one other developer working on a similar module, however he has not released his code. http://drupal.org/node/881040 In fact he references my group post, as well as http://mosaic.arizona.edu/jira/open which is the site that I built this module for originally.
The only other JIRA module I was able to find provides authentication integration, using JIRA as the user authentication source, but does not do anything with issue/node integration.

joachim’s picture

joachim commented
Status: Needs work » Needs review

Could this be done in a more flexible way as a Feeds plugin?

MarkFischer’s picture

MarkFischer commented

Could this be done in a more flexible way as a Feeds plugin?

I had not thought to write it in such a away. Its quite possible that it would be more flexible as a Feeds plugin. At this point I don't have any plans to rewrite it for Feeds, especially not for 6.x. When I need to upgrade this module for 7 it would certainly make sense to look at that path. Right now the module is finished, and I was just hoping to share it with others.

wfx’s picture

wfx commented

Thanks for sharing this with the community!

zzolo’s picture

zzolo commented
Component: Miscellaneous » miscellaneous
Status: Needs review » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
Ari Gold’s picture

Ari Gold commented

Hi MarkFischer,

Are you planning on moving this application forward?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Closed (won't fix)

The OP didn't give any feedback on this. I am closing this application.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: miscellaneous » new project application
Issue summary: View changes