Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.3.2
    • Fix Version/s: None
    • Component/s: JIRA
    • Labels:
      None
    • Environment:

      win 7, 64 bit

    • Sprint:
      to nuke

      Description

      Local searches- never display anything.
      Saved searches on the Jira server do not appear in the connector (ensured using the same account as used when adding the server to the connector.)

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jgorycki Janusz Gorycki (Inactive) added a comment -

            Hi,

            The connector uses XML view of the filter to retrieve fiter results.

            Could you try to check what your XML filter view contains? Steps to reproduce are shown in the attached image.

            Regards
            Janusz

            Show
            jgorycki Janusz Gorycki (Inactive) added a comment - Hi, The connector uses XML view of the filter to retrieve fiter results. Could you try to check what your XML filter view contains? Steps to reproduce are shown in the attached image. Regards Janusz
            Hide
            kiwikid Julian Rendell added a comment -

            Some observations:
            1. executing 'view in browser' > takes me to our jira server's web interface, but I can't view the query not logged into the browser. Understandable, but raises the question: does the connector authenticate correctly for retrieving saved and local searches?
            2. We are using Jira 4.3.2 - I can't find a way to view the query as XML (results, yes, but not the query.) I'm new to Jira- I assume there is a server setting that will allow this? Please let me know how to enable this, and I'll ask our admin.
            3. After logging into Jira in the browser, and then 'view on server' in the connector, the local query is: "project = PROJECT_NAME AND affectedVersion = xxx AND fixVersion = xxx ORDER BY component ASC, key DESC". HOWEVER I had only selected the project name in the connector. I don't know where/why the version field are being included, or where these values are coming from.
            4. More important to me is getting saved searches on the server appearing in the connector (so I have a canonical place for my searches/can be shared with my team.) Is there a log file I can enable to get an idea why this is failing?

            Show
            kiwikid Julian Rendell added a comment - Some observations: 1. executing 'view in browser' > takes me to our jira server's web interface, but I can't view the query not logged into the browser. Understandable, but raises the question: does the connector authenticate correctly for retrieving saved and local searches? 2. We are using Jira 4.3.2 - I can't find a way to view the query as XML (results, yes, but not the query.) I'm new to Jira- I assume there is a server setting that will allow this? Please let me know how to enable this, and I'll ask our admin. 3. After logging into Jira in the browser, and then 'view on server' in the connector, the local query is: "project = PROJECT_NAME AND affectedVersion = xxx AND fixVersion = xxx ORDER BY component ASC, key DESC". HOWEVER I had only selected the project name in the connector. I don't know where/why the version field are being included, or where these values are coming from. 4. More important to me is getting saved searches on the server appearing in the connector (so I have a canonical place for my searches/can be shared with my team.) Is there a log file I can enable to get an idea why this is failing?
            Hide
            jgorycki Janusz Gorycki (Inactive) added a comment -

            ad 1. yes, the connector authenticates properly. Unless it does not, which would mean there is a bug in it . But let's assume at this point that auithenticatin is fine

            ad 2. XML query indeed is not trivial to construct. For saved filters, it is something like:

            <jira-url>/sr/jira.issueviews:searchrequest-xml/<filter-id>/SearchRequest-<filter-id>.xml?tempMax=1000
            

            Where jira-url is the base URL of your JIRA and <filter-id> is a numeric ID of your saved filter (they start from 10000 - you can find your saved filter ID in your saved filter URL - it in the requestId parameter)

            ad 3.
            The fact that fixVersion is there in the filter query is weird. Are you sure you did not specify fix version in the fiter definition in the connector? Note that fix version is one the "Components/Versions" tab (not selected by default). I find it a bit puzzling why this could happen. Please see the end of this comment for an idea how to debug this problem

            ad 4. saved search URL is described in my response to your question #2.

            I think it would be a good idea to find out what URLs are queried by the connector by consulting your web server log. If your JIRA is fronted by Apache, the log will be somewhere in the file named access.log (usually /var/log/apache2/access.log). For IIS, I am not sure where access logs are.

            Show
            jgorycki Janusz Gorycki (Inactive) added a comment - ad 1. yes, the connector authenticates properly. Unless it does not, which would mean there is a bug in it . But let's assume at this point that auithenticatin is fine ad 2. XML query indeed is not trivial to construct. For saved filters, it is something like: <jira-url>/sr/jira.issueviews:searchrequest-xml/<filter-id>/SearchRequest-<filter-id>.xml?tempMax=1000 Where jira-url is the base URL of your JIRA and <filter-id> is a numeric ID of your saved filter (they start from 10000 - you can find your saved filter ID in your saved filter URL - it in the requestId parameter) ad 3. The fact that fixVersion is there in the filter query is weird. Are you sure you did not specify fix version in the fiter definition in the connector? Note that fix version is one the "Components/Versions" tab (not selected by default). I find it a bit puzzling why this could happen. Please see the end of this comment for an idea how to debug this problem ad 4. saved search URL is described in my response to your question #2. I think it would be a good idea to find out what URLs are queried by the connector by consulting your web server log. If your JIRA is fronted by Apache, the log will be somewhere in the file named access.log (usually /var/log/apache2/access.log). For IIS, I am not sure where access logs are.

              People

              • Assignee:
                jgorycki Janusz Gorycki (Inactive)
                Reporter:
                kiwikid Julian Rendell
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Who's Looking?

                    Agile