JIRA Extended Participants

Name JIRA Extended Participants
Version 1.0.2 for JIRA 3.11-3.12
Version 1.0.1 for JIRA 3.9
Author(s) Jean-Baptiste Catté
Price Free
Download JAR jira-extended-participants-1.0.2.jar
Download Source jira-extended-participants-1.0.2-src.zip

Description/Features

Add user custom field support to the partcipants custom field from jira-toolkit. You can select one user custom field and it will be part of the participants.

Installation

  1. Put the plugin jar into the atlassian-jira\WEB-INF\lib directory.
  2. Configure jira-extended-participants.properties and put it into the JIRA working directory (bin/).
  3. Restart JIRA.

Changelog

1.0

Initial version.

1.0.1

Add missing searchers.

1.0.2

Update for JIRA 3.11

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 30, 2007

    Jack Baty says:

    Will this then allow for notification rules to include all participants? That wo...

    Will this then allow for notification rules to include all participants? That would be very helpful.

    1. Jul 11

      Sascha Wojewsky says:

      Hi, do you have got any answer for this?

      Hi,

      do you have got any answer for this?

      1. Jul 11

        Jack Baty says:

        Yes, "Participants" is included in the list of User Custom Fields when adding a ...

        Yes, "Participants" is included in the list of User Custom Fields when adding a notification. At least it does for me. I don't recall if I needed to do anything special to make that happen though.

  2. Jul 11

    Sascha Wojewsky says:

    Thank you for this plugin. I've a little problem. I don not know where to put th...

    Thank you for this plugin.

    I've a little problem. I don not know where to put the "jira-extended-participants.properties" File? I have not any bin directoy...

    Greetings

    Sascha

    1. Jul 11

      Jean-Baptiste Catté says:

      Are you sure you are running JIRA? ;) Which version on which platform are your ...

      Are you sure you are running JIRA?
      Which version on which platform are your running? As far as I know you should have a bin directory in any case.

      1. Jul 11

        Sascha Wojewsky says:

        Sorry for my question, but I'm a newb in JavaApplication... I'm using Jira Enter...

        Sorry for my question, but I'm a newb in Java-Application...

        I'm using Jira Enterprise 3.12.3 war/ear Version (not Standalone) with Tomcat 5.0 and Linux.

        1. Jul 11

          Jean-Baptiste Catté says:

          No Problem ;) As you are not using the standalone version of JIRA, I think you h...

          No Problem
          As you are not using the standalone version of JIRA, I think you have to put the file in the bin directory of your Tomcat installation beside of the startup.sh file (execution directory).

          1. Jul 11

            Sascha Wojewsky says:

            I've found the startup.sh in /usr/share/tomcat5/bin. I've copied the config to t...

            I've found the startup.sh in /usr/share/tomcat5/bin.

            I've copied the config to this location but it doesn't work (partcipants were only the developer)...

             Is anywhere a logfile for this?

  3. Aug 21

    Alexey Serba says:

    Hi JeanBaptiste, Configure jiraextendedparticipants.properties and put it int...

    Hi Jean-Baptiste,

    Configure jira-extended-participants.properties and put it into the JIRA working directory (bin/)

    It seems it would be much convenient to put this file into application's WEB-INF/classes and use

    ExtendedParticipantsCFType.java
    properties.load(this.getClass().getClassLoader().getResourceAsStream(USER_CUSTOM_FIELD_FILE_NAME));

    instead of

    ExtendedParticipantsCFType.java
    properties.load(new FileInputStream(USER_CUSTOM_FIELD_FILE_NAME));

    Hope it helps,
    Alex

    1. Aug 21

      Alexey Serba says:

      One more thing currently getUserCustomField prints exception with ERROR level if...

      One more thing - currently getUserCustomField prints exception with ERROR level if 1) property file is absent 2) you don't have any custom USER fields. It seems it would be great to reduce debug level to DEBUG or INFO.