Assign To Role Member workflow function

Added by Stanislav Laufik, last edited by Brian Hegeman on May 07, 2008  (view change) show comment
Name AssignToRoleMember
Version 1.3.2
Product Versions  
Author(s) stanoislav
Homepage  
Price  
License  
JavaDocs  
IssueTracking  
Download JAR 1.3.2
Download Source 1.3.2

Description/Features

This plugin contains 2 functions: 1. Assign the isssue to a default member from the specified role for the project 2. Assign the issue to the last member from the specified role that had this issue assigned before
Both workflow functions are configured with a role name (e.g. QAMembers, Developers, etc.).

When the first function is executed it finds the default user assigned to the configured role for the current project and assigns the issue to that user. However JIRA currently doesn't have a way to specify which user is the default user in the project role. For that reason the plugin is using "hacky" workaround. It will look through the list of all users in the specified project role and try to find a user that has a custom property set in the following format:
property name: [ProjectName]x[RoleName] (for example: CoolProjectxQAMembers)
property value: default
When it finds a user with such property it will consider this to be teh default user in this project role. If there is no user with such a property in the specified role it will simply assign it to the first user.
(You can set custom user properties by clicking Edit Properties in the user administration module)
This can be used for scenarios like: "when a developer resolves the issue assign the issue to the QA lead"

When the second function is executed if goes through the change history of the item. When it finds a user that belongs to the configured role it assigns the issue to that user. This can be used for scenarios like: "when QA fails the bug assign it to the last developer that was working on it"

Installation

Standard JIRA plugin installation (copy jar to atlassian-jira\WEB-INF\lib)

Usage

Examples

Version History

1.0 Assign to the default user from the specified role
1.1 Added Assign to the last user from the specified role
1.2 Switched to use project level projectroles
1.3 Bugfix release (the Assign To Last function was checking only the last item in the change history)
1.3.1 Bugfix release (now looks through history of previous assignees, not history of users who changed the issue as described in this comment thread); changed name in JIRA Administration Plugins page to "Assign to role member"
1.3.2 Another Bugfix release. Now can correctly assign to the initial assignee of an issue. Thanks to Christine and Damian who originally reported the problem in comments below

Open Issues

Screenshots

   

Labels

workflow workflow Delete
plugins plugins Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (46)

 

  1. Jun 20, 2007

    sameer danthurthy says:

    It would have been great if it actually used the roles in the project rather tha...

    It would have been great if it actually used the roles in the project rather than just the default members in a role. That way the entire team management could be delegated to the team lead as opposed to the administrator

    1. Jun 21, 2007

      Stanislav Laufik says:

      can you explain it bit more pls? do you mean assigning to everybody that has the...

      can you explain it bit more pls? do you mean assigning to everybody that has the role? (multi-user assigning?)

      that i think cannot be achieved in a plugin, as the jira core doesnt support having an issue asigned to more then one person.

       or did i not understand your comment correctly?

  2. Jun 21, 2007

    sameer danthurthy says:

    Lets take the following example #1. Jira Admin defines roles using "pr...

    Lets take the following example

    #1. Jira Admin defines roles using "project role browser" with default users.

    #2 Project admin defines/edits the members in each of those roles for their own projects overiding the previous setting from #1.

    If the plugin could use user from #2 unlike #1 ( as id does now ), it could be great utility. This way jiraadmins can define a single workflow for all the projects and assign the transitions to roles instead of groups. Project admins can define any person in that role and thus not depend on jira admin to maintain the rosters for them.

    In your example ""when a developer resolves the issue assign the issue to the QA lead""

    The QA lead could be different for each of the projects, however the workflow could be same and so ideally, the default QA lead is "overridden" by the "QA Lead" at the project level. (BTW:- iam talking in the context of enterprise version)

    Hope this helps.

    1. Jun 22, 2007

      Stanislav Laufik says:

      thank you, that makes sense. I have updated the plugin to use members in the ro...

      thank you, that makes sense.

      I have updated the plugin to use members in the role for the current project instead of the global members. However because on that level there is no "default" user I had to use a not-so-pretty user property workaround. Pls see the description above for details.

      Pls let me know if this solution makes sense or you see some enhancements that could improve this.

  3. Jun 22, 2007

    sameer danthurthy says:

    This is perfect, I will test it out over the weekend. This would be much need re...

    This is perfect, I will test it out over the weekend. This would be much need relief from the resticted functionality that Jira offers. I think the "group" functionality that Jira offers is not useful, the project tole functionality is a great one and this plugin could streamline the maint. overhead the Jira stipulates.

  4. Jun 27, 2007

    sameer danthurthy says:

    Looks like it's been working just fine. I think this plugin is a lifesaver.

    Looks like it's been working just fine. I think this plugin is a lifesaver.

  5. Jun 27, 2007

    sameer danthurthy says:

    found a problem.. Let's say that issue was assigned to "QA Lead" role which has...

    found a problem..

    Let's say that issue was assigned to "QA Lead" role which has userqa as the only user. The issue is assigned to this user. However in the summary view "

      Open Issues: Assigned To Me (Displaying 0 of 0)  

     portlet, the issue is not assigned to the user usserqa, but when I open the detailed view of the issue, it shows as if it's assigned to the userqa. Hope it makes sense.

    In the summary view the issue is "unassigned", in the detailed view it's assigned to userqa.

    1. Jun 28, 2007

      Stanislav Laufik says:

      I was confused by that too! It has turned out to be this problem http://jira...

      I was confused by that too! It has turned out to be this problem http://jira.atlassian.com/browse/JRA-9501. We ended up creating a new defaut filter called "My Issues" that lists all assigned issues of the current user that don't have status closed (no matter what is the resolution). http://confluence.atlassian.com/display/JIRA/How+to+create+a+custom+preset+filter

      Do you think you are facing the same issue?

      1. Jun 28, 2007

        sameer danthurthy says:

        I have attached a screenshot and sent it to your email. I wish this forum had a ...

        I have attached a screenshot and sent it to your email. I wish this forum had a way to attach documents.

        I thought it was due to the issue that u described and checked it out yesterday, but in the isseu navigator, i see the issue "Unassigned", but in the detail view it's assigned to a person. Pls check your hotmail.

        Thanks

        1. Jul 10, 2007

          Stanislav Laufik says:

          Just to keep this thread updated - Sameer was able to resolve the issue...

          Just to keep this thread updated - Sameer was able to resolve the issues.

          What is helpful when when troubleshooting the assignments is to look at stdout_[date].log file in [JiraInstallationFolder]\logs. It contains a log of teh activity of teh plugin.

  6. Jul 18, 2007

    Michael Reker says:

    Hi! First of all, thanks for the plugin. I guess I found a bug or so. Whe...

    Hi!

    First of all, thanks for the plugin.

    I guess I found a bug or so. When you retreive the previous assignee you take the name from the changed by field in the change history block right?

    Problem what I found is that when for example I (and I am also in a dev role amongst other roles) manually assign a new developer from the dev role instead of the previous developer and in the next transition the previous developer should be assigned again, what happens is that I (who changed it manually) am assigned (even when I am not involved in the project). This is not desirable of course.

    So is there a possible solution to this problem? Thanks in advance. 

    1. Oct 18, 2007

      Brian Hegeman says:

      I've experienced this problem too. Just to be clear, the Assign to Last Role Mem...

      I've experienced this problem too. Just to be clear, the Assign to Last Role Member function looks through the history of users who have changed the issue, not through the history of users to whom the issue has been assigned.

      I would expect the latter behavior and indeed the documentation suggests that...

      I think the following code is the source of the problem.

      com.atlassian.jira.plugin.workflow.function.AssignToLastRoleMember.AssignToLastRoleMemberFunction : 83
      ...
User user = changeHistoryItem.getUser();
...

      Haven't worked out a way to fix it yet...

      1. Nov 09, 2007

        Stanislav Laufik says:

        I dont know that much about Jira; I didnt realize I should be looping through a ...

        I dont know that much about Jira; I didnt realize I should be looping through a different list. I will try to see if I can figure out what you are refering to. (If anybody figures it out sooner pls feel free to post the modified version, the source code is attached)

        1. Nov 13, 2007

          Brian Hegeman says:

          Stanislav, I have a fix for this bug and I can attach the modified src and binar...

          Stanislav,
          I have a fix for this bug and I can attach the modified src and binary when I have a chance to clean up the source and package it all. Any requests for how I name the files?

          Again, thanks for the excellent plugin! Fixing this issue required only changes to com.atlassian.jira.plugin.workflow.function.AssignToLastRoleMember.AssignToLastRoleMemberFunction.

          N.B., I also changed the plugin name in atlassian-plugin.xml as it was misleading before. The name is now "Assign to role member" instead of "Assign to group member" (emphasis mine); this change is seen the plugins list of JIRA admin.

        2. Nov 13, 2007

          Brian Hegeman says:

          I've attached my modified source and compiled .jar as 1.3.1

          I've attached my modified source and compiled .jar as 1.3.1

  7. Sep 05, 2007

    siandallaway says:

    Hi I have encountered exactly the same problem as Michael. I am trying to use ...

    Hi

    I have encountered exactly the same problem as Michael. I am trying to use this plugin to cascade assigning sub-issues to the same person as I'm assigning the main issue to during an automatic workflow transition. Trouble is, it assigns them to me!!

  8. Oct 04, 2007

    Michael Ginnitti says:

    Is there a way to enhance this plug-in,to be used within in a custom field? The ...

    Is there a way to enhance this plug-in,to be used within in a custom field? The scenario I have is, a project gets approved in Step 1 of the workflow. From there the reporter must assign the project to a Role (i.e. Developers, Designers...) I would like to be able to create a custom select box that contains all Roles in JIRA, and upon selecting the role, the project is default-assigned to the Lead of that Role (i.e. the Development Team Lead).

     thoughts?

  9. Oct 25, 2007

    Nicole Wieser says:

    Hi, I've a problem with this plugin. After installation this plugin ( i get no ...

    Hi,

    I've a problem with this plugin. After installation this plugin ( i get no error or entry in the log file) i can't see it in the plugin list and the post function looks still identic.

    My jira version is Enterprise Edition, Version: 3.10.2.

    Why?

    Regards

    Nicole

    1. Oct 31, 2007

      Abdelkader Boumediene says:

      Hi all, I have same issue with Jira 3.11. Thanks, Abdelkader

      Hi all,

      I have same issue with Jira 3.11.

      Thanks,

      Abdelkader

      1. Nov 09, 2007

        Stanislav Laufik says:

        Hi guys Sorry for the late reply. I had some reports of plugin not working, the...

        Hi guys

        Sorry for the late reply. I had some reports of plugin not working, they all turned out to be a problem with the downloaded jar file. Pls try renaming the extention from .jar to .zip and see if you can unzip it without any problem. If not pls try redownloading the JAR file.

         If it doesnt help pls send me an email and I will send you the jar file directly.

        s.

  10. Nov 12, 2007

    Abdelkader Boumediene says:

    Hi all,  It works with version 1.4 I think I met a little bad comportment...

    Hi all,

     It works with version 1.4

    I think I met a little bad comportment.

    I added the following assigning:

    Action Resolve ==>  Planned --> Resolved: Assign the issue to the default user from the QA role.

    Action Reject_Fixe ==> Resolved --> Planned: Assign the issue to the default user from the Developers role.

    Test:

    1. Transition Action Resolve ==>  Planned --> Resolved: ==> OK: issue assigned to a QA member

    2. Transition Action Reject_Fixe ==> Resolved --> Planned: ==> OK: issue assigned to a Developer member

    3. Assign: ==> NOK, list correponds to QA members instead of Developers members

    Any idea?

    Thanks,

    Abdelkader

  11. Nov 28, 2007

    Joshua Standing says:

    Hi, I am trying to setup all the user properties to handle default users for ea...

    Hi,

    I am trying to setup all the user properties to handle default users for each role.  One of our projects has a hyphen in the name and I receive the error:

    The 'key' can only contain alphanumeric characters.

    Is there a workaround for this? I was thinking of creating a bogus alphanumeric key and modifying the propertyentry table directly to reflect the hyphen.

    Thanks

    Joshua Standing

    1. Nov 30, 2007

      Joshua Standing says:

      This workaround worked for me. 1. Stop Service 2. Run Query (our database is m...

      This workaround worked for me.

      1. Stop Service

      2. Run Query (our database is mssql) 

      update propertyentry
set PROPERTY_KEY = 'jira.meta.My Project - SubUnitxMy Role'
where PROPERTY_KEY = 'jira.meta.My Project hyphen  SubUnitxMy Role'

      3. Start Service

    2. Oct 01

      vr says:

      Hi! I almost satisfied with this plugin functionality.  1) I ha...

      Hi!

      I almost satisfied with this plugin functionality. 

      1)

      I have experiences with same problem as Joshua had.

      Why author didnt use id for appropriate reffered entities rather than its names? Is any explanation is here?

      2)

      Could it be possible to chose by default\proposed Assignee of the individual selected by this plugin on a making transition screen? So that the actioning user is able to change proposed Assignee.

      Thanks.

  12. Dec 14, 2007

    Christine A says:

    Hi, great idea, this plugin. Thank you for it ! Is it correct to say that, the ...

    Hi, great idea, this plugin. Thank you for it !

    Is it correct to say that, the second function "Assign the issue to the last member from the specified role that had this issue assigned before" does not take the initial assignee into consideration. That is, if the only assignee who has the specified role was the initial one, ie, not listed in the Change History, then, it will not be found back?

    Is there a workaround for this?

    1. Dec 28, 2007

      Damian Le Gresley says:

      Christine, you are right - I just encountered the same issue myself when using B...

      Christine, you are right - I just encountered the same issue myself when using Brian's modified 1.3.1 plugin.  I have added a 'study' state that allows the issue to be assigned back to the reporter for more information from the open state.  When they have added the necessary information they 'end study' which uses this plugin to re-assign back to the original assignee (to save the reporter having to make the correct reassignment choice).  This does not work on the first transition to study (as there is no change history containing the original assignee) but does work correctly on all subsequent open->study->open transitions.

      Brian / Stanislav - are either of you able to make a fix for this?

      1. Jan 29, 2008

        Brian Hegeman says:

        Christine and Damian, First, sorry for the late reply. I believe I have an idea ...

        Christine and Damian,
        First, sorry for the late reply. I believe I have an idea of what the problem is, I'll have a look later today after the day job

      2. Jan 29, 2008

        Brian Hegeman says:

        Great catch Christine and Damian! I found the issue and have uploaded 1.3.2. Ple...

        Great catch Christine and Damian! I found the issue and have uploaded 1.3.2. Please let me know if that doesn't fix the problem.

        1. Feb 11, 2008

          Christine A says:

          Hi Brian ! Thank you for this fast fix. It does work ! Regards, Christine.

          Hi Brian !
          Thank you for this fast fix. It does work !
          Regards,
          Christine.

        2. Feb 13, 2008

          Christine A says:

          Brian, could it be that this version 1.3.2 also correct a second problem I notic...

          Brian, could it be that this version 1.3.2 also correct a second problem I noticed (but did not report as I did not expect such a great support !): users playing Roles through Groups were not found, I think, in 1.3.1. This seems to be solved in 1.3.2.

          There is noo need to answer (unless I'm wrong ...), but this could be a useful info for people who would also have noticed this ... weakness previously.

          Cheers,

          Christine.

  13. Feb 05, 2008

    Erin Spiceland says:

    Thanks for this wonderfully useful plugin!

    Thanks for this wonderfully useful plugin!

  14. Feb 12, 2008

    Tal Abramson says:

    i felt like i must thank you for this wonderful plugin you saved me a lot of tr...

    i felt like i must thank you for this wonderful plugin

    you saved me a lot of trouble

    so , Thank you very much 

  15. Feb 13, 2008

    Luciene Vieira de Andrade says:

    Resolved

    Resolved

  16. Feb 21, 2008

    Tal Abramson says:

    Assign to to role - causing me a problem i added this post function to the crea...

    Assign to to role - causing me a problem

    i added this post function to the create issue transaction

    but when i press create , it give me an exception (see below) and stay on the create screen

    although it has created the issue , and assigned a user

    any help will be appreciated

    the exception:

    Errors

    • java.lang.NullPointerException at com.atlassian.jira.issue.managers.DefaultIssueManager.notifyTrackbacks(DefaultIssueManager.java:384) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:366) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:313) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at $Proxy9.createIssue(Unknown Source) at com.atlassian.jira.web.action.issue.CreateIssueDetails.createIssue(CreateIssueDetails.java:141) at com.atlassian.jira.web.action.issue.CreateIssueDetails.doExecute(CreateIssueDetails.java:110) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:211) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:192) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:110) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)

    1. Mar 08, 2008

      Christopher G. Stach II says:

      In the Create transition Post Functions, move the assign module below "Creates t...

      In the Create transition Post Functions, move the assign module below "Creates the issue origi