Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Custom fields in Proforma for Jira Service Management (Cloud)

Hello! Since Proforma is a part of JSM we have started actively using forms. 

One thing we have noticed, if you connect the custom field, and the custom field has different contexts, it looks like only default context works with proforma. Is that alright? Sorry, can't find it in the documentation and want to confirm whether this is a bug, or can be a feature request for Atlassian. Or maybe there are some workarounds? 

1 answer

Heya, I can't provide a remedy but I did experience the same thing!

I had a form input field set up that was linked to a checkbox JIRA custom field named Applications.
I then added a custom field context so I could use it for another form that included applications.

The first form with the applications checkbox field then broke, being unable handle more than one context.

Potentially we have to create a separate custom field for now...

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events