Linking Issues in one Project to the Portal

[Deleted user]

I use a Jira Project for managing my project. The organisation is using Jira Service Manager to manage service request tickets and has set up a portal. I have raised a service request and been allocated a Jira number (xyz-1800, say). The service request Jira is a blocker in my project so I have linked the xyz-1800 Issue to an Issue in my project (MP-123, say).

My problem is that my Issue number MP-123 is displayed as a blocker in the portal screen for xyz-1800 but I am unable to see the Jira service manager Issue number - xyz-1800 - in my project.

Is this a security/access issue or a limitation of Jira Server?

[vkharisma]

Hi Gregory,

It seems that you have ran into a known issue in Greenhopper:

https://jira.atlassian.com/browse/GHS-9193

As a workaround, you can *unlock* the GH custom fields and rename it to a suitable name. You can refer to the bug ticket above for the detail steps on renaming the custom fields.

Cheers,

[Gregory Demotchkine]

Is this issue going be fixed ? why does it happen ?

I read the link you have sent, it's frightening and this just should not be MY headache. :)

A paid addin which cannot display properly it's own MAJOR custom fields - disgusting:!

1) makes this look totally unprofessional when show this to my higherups

2) I worry if I implement this fix that this will end breaking something else now or in later evolutions in JIRA / JiraAgile

After all if I am modifying these fields for friendly names, this does not touch the db schema ? So ok, I'll have to rework some filters, but will JiraAgile know what fields to call ?