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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Good/best practice: Custom field context for each request type?

I encountered some design challenges/questions in my new JSM Cloud project.  Please give some suggestions.

- Request types for portal:

1) Password & Account 2) Email & Calendar 3) Print and Scan 4) Internet & Infrastructure 5) Software and Application 6) Computer and Other Hardware 7) Telephony 8) Generic IT request

- A custom field "Asset category".  Currently I am thinking of cascading selection field

Parent level:

Desktop Application, Enterprise Application, Business Application, &

Computer, Tablet, Monitor, Printers, Peripherals, &

Network, Server, Storage, &

Phones, Calling Report, Video Conferencing

...

Children level for Desktop Application:

Adobe Acrobat, Google Chrome, Microsoft Word, Microsoft Excel, ....

...

I want the parent level options of the cascading field are limited based on request type.  But how can it be achieved?

Approach 1: Creating many asset category fields such as "Asset Category-Application", "Asset Category-Hardware", "Asset Category-Infrastructure", "Asset Category-Telephony", etc.  The Cons for this one is too many fields for effective reporting. 

Approach 2: One cascading field with a context for each request type.  Because context is tied to "project+issue type".  Then I need to have many issue types.  such as incident for application, incident for hardware, support request for application, support request for hardware, etc.  Probably too many issue types to be efficient I guess.

Please help me out with some good/best practice here.  Thanks much!!

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

690 views 10 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you