You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Currently i'm able to set a Custom field context based on 2 factors
Issue type & Project.
Is it possible to have sepperate contexts on other factors as well?
some examples that would be really helpfull to me
Portal view vs backoffice view (Jira Service Management)
Issue create view vs Issue edit view (similar to screen schemes)
Basically i would like to have different options available based on these 'states'
one example is for my assets view, where i can use context to set different behaviours (filters) based on the project it's in.
I would like to be able to split this up for use in portal vs use in backoffice.
No, that's not possible as far as contexts go. But can you be a little more specific about the use case(s). For instance, You can put a field on a the Create Screen or the Edit Screen or both or neither already, so not sure what the context would do differently.
I have an example with Assets.
i use assets as a CMS system, meaning i have my users & organizations from JSM in assets, and use API to manage them from there.
On the portal view from JSM i need the Assets custom field to filter out the Organizations based on the current reporter.
BUT on issue create screen on the backoffice side (using the create button, same project/issuetype otherwise) i want this to act differently by means of using a different context.
Yeah, that one is beyond me. I suggest you open a support ticket with Atlassian to see what they say. Please post back here with the solution so future readers will know the answer. Good luck!