Why the GreenHopper XML tags in non-GreenHopper project issues?

We use GreenHopper and are upgrading both our JIRA (from 4.0 to 5.1) and our GreenHopper. I m currently running tests on a test environment and we have noticed the following:

If I open an issue for a project that is not agile (i.e. a proper JIRA project) and view it in XML, it contains GreenHopper XML tags. Why is that and can they or even should they be removed? What is their purpose?

These tags do not exist in our current production JIRA 4.0. so they seem to be an addition in the newer JIRA/GreenHopper versions.

FYI, we use the XML format of an issue to process it in a deployment system and connect it to a software delivery (our deployment system is a system from which we deliver our software products).

1 answer

1 accepted

0 votes
Accepted answer
Ahmad Danial Atlassian Team Nov 19, 2012

Hey there, Patrik.

As mentioned in the support ticket that you have raised, we hope that the explanation provided to you was sufficient.

Warm regards,

Danial

Hello!

Yes it was.

Thank you for your reply and sorry about my late reply.

Regards Patrik

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Jira Service Desk

Looking for anyone who has switched from Zendesk to Jira Service Desk

Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk!   We’d love to hear your thoughts on the pros and ...

21 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you