Restricting custom fields in JQL search

[Srikanth Ganipisetty]

Hello,

We have similar name 4 custom fields.. and these are being used by several projects Ex: SystemFix, System fix, System, System2 with having their own options. 

How do I make sure that the users don't get confused while searching for results and for generating reports? Unless the user knows these difference, they can't really make use of these custom fields using JQL search. 

Note: I checked in field configurations ( to hide these fields and restricted them only to their relative projects).

I fixed the contexts, search templates too. but these are just only restricting them to it's project from project, issue type from issuetype... How can we stop recommendations in JQL when we assign Project=A AND Sys (showing all the possible options)?? I wanted to restrict this to be project =A AND Sys ( MUST show only Systemfix) as we mentioned in field configurations, screens, search templates that this field belongs to project A? 

Also, we are feeding these data using REST API's, so we can't reply on Multi context concepts, as they all carry same custom field ID, which can't be handled in code. 

Is there any work around solution I can use? Or with Marketplace Apps? 

Thanks,

Srikanth Ganipisetty

[Tim Perrault]

Hi @Srikanth Ganipisetty 

Are they all the same type of field or are they different types?

Thanks,

Tim

[Srikanth Ganipisetty]

Hi @Tim Perrault  

Different types, do you have solution for same type maybe? 

Thanks,

Srikanth Ganipisetty

[Tim Perrault]

If they were all the same type of field, then you could have just one field with different configurations for each project. This would give you one field, but every project could have different options.