Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71959

Jira behaves differently on different version with using a same Element plugin

XMLWordPrintable

      Issue Summary

      A customer is using the plugin Elements connect external data fields to filter out the groups who can access issues in his project.
      On reproducing in as below,

      • the functionality works fine in v7.13 > User is able to access the issue if he is present in the group and able to see the issue when filtered using JQL as well.
      • In 8.0 and above (tested in 8.5.10), user can access the issue successfully but the issue is not returned while running the JQL.

      Steps to Reproduce

      • Install Elements connect external data fields
      • Create an Elements Connect Live Text (Legacy) custom field, plugged on the local datasource (SQL)
        Use this query: select group_name from cwd_group
        Key: 0
        Template: {0}
      • Create a new project (with TEST as Key)
      • Edit the Permission Scheme associated to this project
      • Give the Browse Project permission only to the previously created Elements Connect custom field (i.e. remove default permission for logged in user)
      • Put the field on all the project's screens
      • Create a new ticket in this project (TEST-1)
      • On the creation screen, select the "jira-administrators" group (in which your user is supposed to be)
      • Browse to the issue navigator

      Expected Results

      The issue TEST-1 created above is visible in the JQL results

      Actual Results

      The issue TEST-1 created above is not visible

      Workaround

      The Jira in built group picker field works fine.

            [JRASERVER-71959] Jira behaves differently on different version with using a same Element plugin

            Sébastien Delcoigne added a comment -

            Hi pczuj,

            From our understanding, a customfield needs to implement GroupSelectorField to be usable for use in project permissions.
            As of Jira 8, this interface defines a single method List<String> getIdentifiersForGroup(String groupName). From the documentation,
            this method is supposed to return all possible IDs a group could have been indexed by. In our case, we return a list with just the group name. The implementation is the same as the group picker customfield which corresponds to how our values are found in the indexes.

            Where could we find a detailed explanation of how these project permissions are evaluated with regard to custom fields ? How are the different values fetched ? When we test our code, the getIdentifiersForGroup method is called as expected but somehow what we return does not work.

            Any help would be greatly appreciated.

             

            Regards,

             

            Sébastien Delcoigne - Elements Connect Developer

            Sébastien Delcoigne added a comment - Hi pczuj , From our understanding, a customfield needs to implement GroupSelectorField to be usable for use in project permissions. As of Jira 8, this interface defines a single method List<String> getIdentifiersForGroup(String groupName). From the documentation , this method is supposed to return all possible IDs a group could have been indexed by. In our case, we return a list with just the group name. The implementation is the same as the group picker customfield which corresponds to how our values are found in the indexes. Where could we find a detailed explanation of how these project permissions are evaluated with regard to custom fields ? How are the different values fetched ? When we test our code, the getIdentifiersForGroup method is called as expected but somehow what we return does not work. Any help would be greatly appreciated.   Regards,   Sébastien Delcoigne - Elements Connect Developer

            Nicolas Esteves added a comment - - edited

            Hi pczuj,

            Thank you for your feedback.

            We are currently working on this topic. We will get back to you soon with the desired information. Thank you for your patience.

            Have a nice day.

            Kind regards,
            Nicolas Esteves - Head of Customer Support at Elements

            Nicolas Esteves added a comment - - edited Hi pczuj , Thank you for your feedback. We are currently working on this topic. We will get back to you soon with the desired information. Thank you for your patience. Have a nice day. Kind regards, Nicolas Esteves - Head of Customer Support at Elements

            Przemyslaw Czuj added a comment -

            Hi sthottamkara@atlassian.com and issue watchers,

            I believe we will not be able to verify if this issue is valid without reproduction steps that don't involve installation of 3rd party plugin. Would it be possible to complete the steps with explicit explanation of Jira plugin module API usage that causes the issue?

            Przemyslaw Czuj added a comment - Hi sthottamkara@atlassian.com and issue watchers, I believe we will not be able to verify if this issue is valid without reproduction steps that don't involve installation of 3rd party plugin. Would it be possible to complete the steps with explicit explanation of Jira plugin module API usage that causes the issue?

              Unassigned Unassigned
              sthottamkara@atlassian.com Sandhya Thottamkara
              Affected customers:
              3 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated: