set default issue type

Issue #496 resolved
Scott McDonald created an issue

Hello -

Is there functionality (post-function) to set the default issue type no matter what the end-user selects as the issue type?

Example: We always want Triage to be the default type but in the issue type drown down, we grant the users ability to select risk, bug, etc.

Comments (5)

  1. Fidel Castro Armario repo owner

    Hi Scott,

    What you can do is to insert a validation in "Create Issue" transition in the workflows of all issue types but Triage, and prevent the creation to any end-user. In order to determine whether a user is end-user or not you can use project roles. You can even implement the restriction if you share the same workflow among different issue types.

    In "Limit Issue Creation per Project Role and Issue Type" you have a detailed explanation on how to do it.

    With this solution the users keep seeing all the issue types in the select list, and they can fill the form to create the issue, but once they try to submit for issue creation, a custom error message is shown informing the user that he/she is not allowed to create the issue type, and that the only issue type allowed to him/her is "Triage".

    Please, let me know if you have any doubt on how to implement this solution.

    Regards,

    Fidel

  2. Scott McDonald reporter

    Thanks. I attempted to add Limit Issue Creation per Project Role logic in my workflow, however, no message is appearing after I select create. Here's the logic I have in place:

    Screen Shot 2017-02-03 at 2.02.59 PM.png

  3. Fidel Castro Armario repo owner

    Hi Scott,

    I have just tried that some configuration with JIRA Workflow Toolbox 2.2.1 on JIRA 6.2.3, and the message is appearing as expected, i.e., when the user doesn't have role "Administrators".

    Please, double check your configuration:

    • Did you published the draft of your workflow?
    • Check that the user you are logged in with has not project role "Administrators".

    In you keep having problems, we can have a video-conference with screen-share in order to see the failure in direct.

  4. Scott McDonald reporter

    Hi Fidel -

    This was on me. I had a user group tied to the project admin role as well that I was a part of (had to dig for it). I removed that group and I am now seeing the following message upon create "You need project role "Administrator" to create this type of issue."

    Thank you! Scott

  5. Log in to comment