The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
- Community
- Q&A
- Jira Service Management
- Questions
- Fields: Request type v Issue type
Fields: Request type v Issue type
Within Jira SD can you have some fields "on" for certain request types but "off" for others, within the same "umbrella" issue type?
Basically we want to group things that have a common workflow under the "Service Request" issue type - so whilst there would be some common fields, there would be others that are unique to their own request type (for example, "Promote Change" would have fields for environment, platform etc - "Add Developer" wouldn't, but they'd both come under the "Service Request" workflow).
Looking at Jira SD now, it looks as if a field will be shared across all the different request types within that issue. That means some requests will contain completely irrelevant fields.
I hope that isn't the case, as that makes me believe I'll have to use either incredibly generic fields, or else create brand new workflows per request type...
Any thoughts?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.