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
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!!
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...
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