Green Hopper introduced issue fields such as Sprint and Rank do not show up when an issue is accessed via the IDE connector using the remote API. Moreover, these fields get reset when an issue is updated using the IDE connector. This causes a previously assigned Sprint issue to fall off the Sprint which can be very disconcerting.
Atlassian Connecotr for Eclipse (v3.0.7)
Atlassian Jira Connector (v3.0.7)
Can you let us know what is your Green Hopper version?
You maight hit the following bug: https://jira.atlassian.com/browse/GHS-5771. It is solved in GH 6.0.4.
We have also scheduled an improvement for Connector 3.0.7 and we will not send uchanged fields so not visible fields will not be erased in case of such issues. You can track the issue here: https://studio.atlassian.com/browse/PLE-1373
Actually there are no plans at the moment. How important is it for you to see these two fields?
Rank is generally used to prioritize issues and the raw number has almost no meaning in the context of single issue, especially because there are gaps between numbers.
Sprint field is more meaningful but I think it should not be editable as there is no dictionary of possible values available so we can't use combo box. Free text field means that users will most likely enter wrong value and issue update will fail. It is hard to edit this field even on the JIRA issue edit page. It is supposed to be changed automatically by GH when issue is added to the sprint.
Please let us know what is your thinking here.
I agree that the GH fields should not be made editable through the connector. Although not critical, it would be nice to display them for informative purposes.
The most important feature for me is to be able to have access to them when creating a new query in Mylyn. It would be really beneficial to be able to run a query like "All issues assigned to user X in Sprint Y sorted by Rank".
In answer to "how important is it to see the fields":
It's hugely important. Rank is what is set when a task if drug up and down in GreenHopper. We are currently hiring on new developers and a PM and defining a more structured process at our shop. I like Jira/GreenHopper. Others here don't. It is (unfortunately) possible that this bug would be enough to push Jira out of our shop.
It's a big deal. I need to be able to tell programmers, "Open mylyn and work on the issues in order." If I have to tell them to keep Jira open in another window, because they can't trust the order in Mylyn, that sucks.
We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...
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!
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