Hello,
I think you may have missed this tooltip while rebranding from GreenHopper to Jira. Just thought I'd point it out.
I'm on Jira Cloud.
Hi Logan,
Thanks for posting this. I understand that when you hover over the sub-task icon found on the parent issue, that the tooltip here is indicating that the sub-task issue type was created by GreenHopper. I tried to recreate this problem, but in my own Jira Cloud site, I don't see the same. Instead when I hover over that icon I just see this:
What I suspect has happened here is that in your specific Jira Cloud site this particular issuetype was actually created by the original GreenHopper plugin (many, many moons ago). It could also be that the issuetype was imported into Jira Cloud at some point these descriptions are expected to be maintained when you do a migration to Jira Cloud. In short, I would wager that issue type was created a long time ago a very old version of Jira.
This is something that your Jira Administrator could change though. A Jira Admin would need to go to > Issues and then find that sub-task issue type and choose the Edit link there. I could understand if you are hesitant to try to change this. The language of that tooltip seems to be actively discouraging you from changing it. I believe that older versions of Jira would have actually locked this field so that you could not change it. But rest assured that in the current versions of Jira Server and Jira Cloud that a Jira admin can change the description of that issuetype. In my system that description reads as
The sub-task of the issue
If I could determine the specific versions of Jira Software that generate an issue type with that description by default, then I could certainly create a bug ticket for that. However all the GreenHopper and Jira Agile versions are way beyond end of life for support now, so it wouldn't ever get fixed in those old products at this point. But I am interested to learn if there is some way in which I can reproduce this today. If there is a way to do this in any currently supported version we can certainly document this and create a bug for it.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.