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.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

JMWE Post Function to Hide Custom Fields

Hi All! 

I have been researching lately the capability to hide custom fields at the user level. After reaching out to Atlassian support, I was told there is no built-in function to do this and that issues can be blocked but not specific content. 

Never one to back down from a challenge, I have been trying to figure out the best way to build this feature myself. We are on a cloud instance, and thought perhaps coding a quick post function that if a user is associated with a certain group when the ticket is created, the specified custom field will be hidden to them. 

While the Nunchucks builder does help me build the code for this (thank goodness, I am terrible at scripting), I can't figure out exactly how to "hide" the field. 

Has anyone experimented with this at all? Any help would be greatly appreciated! 

1 comment

David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 16, 2018

Hi Alys,

Unfortunately, this is simply not possible on Jira cloud, where the API for add-on development is much more limited. 

Comment

Log in or Sign up to comment