title: JIRA vs. Service-Now for Software Project Management
body: <p>The company that I'm working for is going to start using ServiceNow for its IT operations and call-center management and they are looking at its SDLC module for software project management.  However, there is also a push (by me) for using JIRA+Greenhopper+Fisheye+Crucible.</p>
  
  <p>Has anyone out there done a feature by feature comparison of these two tools?  </p>
  
  <p>Using the ServiceNow demo, it sounds like it's quite versatile but I believe it's being customized pretty heavily for our call-center by Service-Now, themselves.  </p>
  
  <p>One of the biggest things that I've liked about JIRA is the extreme level of customization that we can do on our own and morph our processes as a result of our retrospectives.  I'm not entirely confident that ServiceNow can provide that and I would definitely like to hear more.</p>
  
  <p>Some features that I'm wondering about in ServiceNow that I can accomplish with JIRA+Greenhopper:</p>
  
  <ul>
  <li><p>Sprints across multiple projects (Scrum Products in ServiceNow?)</p></li>
  <li><p>Source/Code Review integration like with Fisheye and Crucible</p></li>
  <li><p>Epics management spanning multiple projects</p></li>
  <li><p>Release Management - JIRA Versions vs. ServiceNow Releases - some teams plan out future releases and others simply cut a build-tag based on what looks good on their release branch.  JIRA lets me have different operational processes to help Leads accomplish this to match what they do "in real life."</p></li>
  </ul>
  
  <p>Any other points in differentiation between these two products would be great.  Thanks!</p>