I am having a use case where I am trying to develop a customer portal with custom fields and values in Jira service management.
In that, I have a custom field with a drop-down of multiple values (let's say value1, value2, value3,value4,value5,..). I have created a different organization for different customers/users (like Org1, Org2, Org3) which contain different customers/users.
When customers/users of Org1 organization, log in to the customer portal, I want to make sure that let's say value1 and value2 from the drop-down be visible to them and value 3 or 5 from the drop-down to be visible to only customers/users from Org2 and so on.
Is there any kind of shell/python script(preferable) or any other scripting option possible to develop such thing in Jira service management (cloud) .
p.s: I am newbie to groovy scripting but knows python and shell scripting well.
I have the same problem here, but on a standard field. Are contexts also available for standard fields or is it limited to custom fields?
My use case is to map different values of Priority on different projects. It was working on our hosted instance of JSD, but we lost it with the cloud migration.
Jira field options are not controlled by who is looking at them, the options are controlled by the type of issue being raised and project they are in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nic Brough -Adaptavist- ,
Could you please elaborate little bit more as I didn't get it completely.
(specifically "type of issue being raised and project they are in." )
Regards,
Ninad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't think of a way to explain it differently, beyond rephrasing it - "the option list you see in a custom field is chosen by the project and issue type, not by user".
Maybe an example would help:
Imagine a field called "colour"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, thanks @Nic Brough -Adaptavist- .
So If I understand well, for my need of having different specific values visible in the drop-down for different customers/organizations, I should :
1)Create separate Jira project for those separate customers/organzation i.e group of users and then
2)In each project, create the same customer portal with custom field (which will have in dropdown, only those values that are specific to that organization/group of users/customers)
Hope this is what you're suggesting as it makes sense to me now :) .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that will indeed do what you describe. I had not really suggested it directly, but you're spot on.
To paraphrase it as I think of it, with my example:
You create projects 1 and 2, allowing one set of customers into only project 1, and another into only project 2. You add the Colour custom field to both, but you have two "contexts" for the field. Context 1 is for project 1 and contains the options red, green and blue, and Context 2 is for project 2, and contains options cyan, magenta, yellow and black.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, thanks for this quick guidance Nic and it's much appreciated. I will try to implement it and then accept this as the answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Meanwhile, is there a way I can import a customer portal designed inside one project to other projects?
Regards,
Ninad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, @Darryl Lee /Atlassian Community team,
Can someone please guide me on this or in case, suggest an alternate way to achieve this in a comparatively easy and efficient way.
Regards,
Ninad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no "easy" way to do this - you will need to write a completely new custom field type, including all the configuration settings and user handling code needed. This is not a small project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.