Component default assignee error

Issue #101 closed
Attila Gaspar [META-INF] created an issue

Hi,

Unfortunately the TheScheduler isn't use the Component "Selecting a Default Assignee" settings. After creating an issue the assignee is empty despite of the componetet lead default assignee settings. (If I create an issue by hand (from JIRA Create function), the assignee is correct)

Could you check it?

(https://confluence.atlassian.com/jira/defining-a-component-185729533.html Component Lead The assignee will be set to the component leader. If the component leader is not permitted to be assigned to issues in the permission scheme this option will be disabled and will say "Component Lead is not allowed to be assigned issues". The Component Lead option will also not be available if the component does not have a lead assigned to the component. Instead under this option it will say "Component does not have a lead.". )

Thanks: Attila

Comments (8)

  1. jost

    Hi Attila,

    Thanks for feedback, we will analyze this issue and keep you updated.

    Could you let us know which version of TSP and JIRA are you using?

    Regards,

    Jacek

  2. Attila Gaspar [META-INF] reporter

    Hi Jacek,

    Our version numbers are * JIRA 7.0.4.#70113 * TSP 4.0.2

    Could you reproduce the error? Can I help you something? Our client is waiting for the solution.

    Thanks a lot!

    Attila

  3. jost

    Hello Attila,

    I reproduced this bug. But this happening only in case users which don't have access to the "Assignee" field. Am i right? Please let us know whether this occurs in any other case on your instantiation.

    The fix for this bug will be attached to the next version of TSP - it should be released this week.

    Jacek

  4. Attila Gaspar [META-INF] reporter

    Hi,

    Great news! :) Thanks!

    What do you mean "don't have access to the "Assignee field"? In our configuration * both the "Reporter" and the "Component lead" are in the "Users Role" of the project, and * the permission scheme contains "Assignable Users" and "Assign Issues" permission to the "User Role". * and the "Assignee" field is on the screen of the project

    Attila

  5. jost

    Hello,

    By "don't have access to the Assignee field" i mean that creator have not permissions to "Assign Issues". Please to check if creator of scheduled issue are able to see "Assignee" field on creation issue screen. But it's not all.

    The most important thing is whether at the moment of creating Scheduled Job the creator had the permissions to assign assignee. The creator is the user which is create the Scheduled Job not reporter. The scheduler saves state of fields in moment of the creation so if a field is not displayed / saved, the change settings to it will not do anything.

    However there is workaround this issue. Please just edit those Scheduled Jobs without doing any changes in fields - the missed fields will be append to the Scheduled Job. But remember that creation screen (its second tab on creation wizard) must contains Assignee field.

    Please confirm whether above solution is works for you.

    Jacek

  6. jost

    Hello Attila,

    We have just released new version of TSP. This version should fix your issue. Please give us fedback about it. Is this resolve your issue?

    Jacek.

  7. jost

    Hi Attilla,

    Thank you, best wishes for the New Year!

    Feel free to open new issue in case of any other problem or question.

    Jacek.

  8. Log in to comment