Link Details

Link 557699 thumbnail
User 292778 avatar

By Leonid Maslov
via leonardinius.blogspot.com
Submitted: Feb 12 2011 / 00:57

If you are familiar with JIRA and it's API then you might agree, that some easy operations become a little difficult when it comes to coding (all the workflows, overall JIRA stack understanding, configuration items, integration with other systems etc). The same is especially true when it comes to creating / updating JIRAs issues, which definitely is backbone for issue tracking systems. Some might argue that this type of things should be done by JIRA itself only. And I couldn't agree more. However JIRA tend to become issue-tracking puzzle-building machinery, where JIRA itself is LEGO puzzle only, so plenty of crazy stuff "you better shouldn't do this" or "you are not supposed to do that" is very popular in the JIRA plugin development world ....
  • 1
  • 0
  • 517
  • 4

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Upvoters (1)



Downvoters (0)



    Apache Hadoop
    Written by: Piotr Krewski
    Featured Refcardz: Top Refcardz:
    1. Play
    2. Akka
    3. Design Patterns
    4. OO JS
    5. Cont. Delivery
    1. Play
    2. Java Performance
    3. Akka
    4. REST
    5. Java