Skip to content
The Chat Archive
claude-3-7-sonnet-20250219· Anthropic LMArena Human Preference 140K

If I am setting up a coupled Jira Service Management and Jira Software projects for a…

  1. User

    If I am setting up a coupled Jira Service Management and Jira Software projects for a company where the Issue Type bridge from what a customer submits in JSM to what a company team member works in JS, is it best off have an Issue Type Scheme that applies to both the Service Desk project and the internal project? This is opposed to have the same issue types but grouped under different schemes per project.

  2. Assistant

    For a coupled JSM and Jira Software setup, using a single shared Issue Type Scheme across both projects is generally the better approach. Here's why:

    Benefits of a Single Shared Issue Type Scheme

    1. Seamless Transition: When issues move between JSM and JS, they maintain their issue type without conversion or automation.

    2. Consistent Experience: Both customer-facing and internal teams work with the same issue types, reducing confusion.

    3. Simplified Maintenance: You only need to update one scheme when making changes to issue types.

    4. Reporting Consistency: Cross-project reporting is more reliable with consistent issue types.

    5. Reduced Configuration: Less overhead in managing multiple schemes that contain essentially the same issue types.

    When to Consider Separate Schemes

    There are specific scenarios where separate schemes might make sense:

    • When you need significantly different issue types for each context
    • If you need to restrict certain issue types to only be available in one project
    • When using different workflows is more important than maintaining issue type consistency

    Best Practice Approach

    For your bridge scenario between customer submissions and internal work:

    1. Create one Issue Type Scheme containing all needed issue types
    2. Apply this scheme to both projects
    3. Use request types in the portal to control what customers see/submit
    4. Configure workflows and screens differently per project (as we discussed in the previous question)
    5. Consider using automation rules to enhance the transition between projects

    Example Setup

    Issue TypeAvailable InNotes
    Service RequestBothCustomer submits, team works
    IncidentBothCustomer reports, team resolves
    RFIBothYour example from earlier
    BugBothCould start in JSM, move to JS
    TaskBothInternal work items

    This approach gives you the flexibility to have different workflows and screens per project while maintaining issue type consistency across the bridge.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.