Home › Amen brother: Mercury Quality Center "software turd"

Reply to comment

Thu, 10/25/2007 - 15:14 — charlie.collins

+1 to JIRA/Mercury integration

I begged for that when "QC" came down the proverbial pike. Our QA dept said they would implement something with the JIRA APIs on their own. Then, when that quite expectedly never happened, we suggested they just use the JIRA email interface, to at least get the issues automatically IN JIRA (even if not synced, etc) - and that was blown off too.

Our problems are obviously bigger than the tools. And yet, even with the mild spam posting, I am going to check out JaM-Plugin.

I say that with a HUGE disclaimer though - if you are even considering Mercury, don't. A plugin for JIRA that shows Mercury issues is only advisable when you get rammed with Mercury in the first place, far better off to just stick to JIRA if you can.

Reply

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <img> <a> <em> <strong> <cite> <code> <ul> <ol> <hr> <li> <dl> <dt> <dd> <pre> <b> <h1> <h2> <h3> <blockquote>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
3 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.