Is possible in JIRA to make two different 'create screen' and assign one or the other depending on the role or a user grup ?
i think you can...by modifying the existing workflow.
you will need to create a new "Create" transition
set validators for each "create" to match your criteria and associate your desired screen to the "create issue" operation in your projects "screen scheme"
i just tried to do so...sorry it says "You cannot add a transition to or from the initial action [Create] of a workflow."
forget my answer please as this will only work for transitions that are after "create"
guys..you may upvoted my answer too fast...as i replied too fast...i should better try by myself if i am not sure if my answer will be correct. i updated the answer...
the mentioned solution won't work for "Create"
True - you can have different "create" screens by issue type (and edit and view screens), but that is it, you can't have two create screens for one issue type.
You could use Field Security Plugin (but it's not for free). There you can define which group is allowed to see or edit a field. So you would have all fields in your create screen but client user will see only those fields where they have a view or edit permission.
This is something I need too, or something quite similar. I need it when external users create issues in Jira. I need these issues to go to a status called 'received' where a developer will review the issue before transitioning it to 'Open'.
This is no problem in itself but I need issues that are created by the developers to transition straight into the 'Open' status. This is not possible as it is today.
that is possible with Automation lite for JIRA (Free)! You can trigger an Event on the create-Trasition and check in the Automation-Plugin if the user is in the "Dev-Role" ore something. When its ture, you can fire the transition to "Open"-Status.
Automation is by the way one of the most intristing Free Plugins about Workflow-customizing...
Take a look ;)
(No, im not from this Plug-In Company ...)
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
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