Service Desk Custom field

[Christos Moysiadis]

Hello everyone,

Scenario:

i have a Jira software v7.3.2 instance that i want to integrate to my newest 7.13. Everything is going perfect until i reach the custom fields when i try to import them. The new instance does not have a Custom Field which have the old one. both instances have Service Desk enabled.

The fact is that this custom field is LOCKED and created programmatically and required by Service Desk itself. 

I cannot enable/create or whatever this field and its driving me crazy.

How can it be enabled/shown in the old one and not in the new one?

Except this there are others , which have the same name but translated and they are LOCKED too. Feeling like i am in a hell.

I am sure that i am searching something wrong. 

Plz any help / advice / link could be helpful!

Best regards 

CM

[Alexey Matveev]

Hello,

Make sure that you installed the correct version of Service Desk. It should be 3.16.0 for 7.13.0

[Christos Moysiadis]

@Alexey Matveev

https://community.atlassian.com/t5/Jira-questions/Update-Custom-Field-Version/qaq-p/977556 ... it says Approvals right :) .... i copy paste a wrong error! This still hangs! This integration has 7 projects in sum, and the 1st one is this who needs this field , Its a service Desk. The solution was found for the others of course , by creating and updating to latest version.

here was a question of mine. i noticed the problem and i did it as it should be.

The main test env is a mirror copy of the production one, so its updated! The production instance has not this field , where 7.13.0(JS) & 3.16.0 (SD)!

BUT the old one, which was in version 7.3.2 and service desk 3.3.0 it has it ! 

How can this be possible?

[Christos Moysiadis]

@Alexey Matveev

is it possible this field to be "enabled" because of an another plugin except service Desk? 

if yes, is it ethical to install the plugin as a free trial in my production system ,do the integration and then uninstall it? 

Best regards 

CM

[Christos Moysiadis]

And again sorry! 

The main problem in this system is the random translations of every possible part of it.

The field was translated in German while the other was in English. Sorry @Alexey Matveev for the time that u spend on this.

now i should find a way to match this two same fields with different name. 

Kind regards and sorry again,

Christos Moysiadis

PS .... please people keep the default! English is so easy sometimes! dont make your life complicated . thnx