Latest Cloud version of JIRA seems to have significant behavioral changes, some borderline erroneous

[Dinu Radian]

A. If I 1. select a Project, 2. go to review the Issues, which causes the display of All issues in the project 3. Select Advanced Search option, and then 4. select Done issues , the Done issues list includes ALL issues of statusCategory=Done regardless of my project selection in step 1 (???) . This is inconsistent with the previous behavior, and - in general - with the expected behavior.

B. If I 1. select a Project, 2. go to review the Issues, which causes the display of All issues in the project, 3. Select Advanced Search option, which opens a Search page for all project issues, 4. select and open the record of one of the listed issues and then 5. use the Back arrow in the browser to go back to the Search page, the navigation to the Search page fails (???). NOTE: A message asserted at the bottom of the screen indicates "Waiting for..." 

C. If I 1. select a Project, 2. go to review the Releases, which causes the display of Releases in the project, 3. Select one such release, which opens the Version page showing the number of Warnings, Issues in version, Issues done, Issues in progress and Issues to do, 4. select the option View in Issue Navigator, 5. select and open the record of one of the issues in the Search list and 6. use the Back arrow in the browser to go back to the Search page, the navigation to the Search page fails (???). NOTE: A message asserted at the bottom of the screen indicates "Waiting for...".

D. At step #5 in the previous example the Search expression indicates instead of the project Key an ID which cannot be easily recognized, and instead of the version Name another ID which again cannot be easily recognized (for example, "project = 11033 AND fixVersion = 12300 ORDER BY status DESC, priority DESC, key ASC" .Why?

I have been using JIRA for 10+ years, both with Server and Cloud installations, and I am quite sure these are new behaviors. 

[Ste Wright]

Hi @Dinu Radian 

I ran through your scenarios. I've clarified each scenario just to confirm we're doing it the same way.

----------------

Scenario A:

1. Went to Projects > Selected a Project
2. On the left-hand menu, selected Issues (viewing "All Issues")
3. Pressed the hyperlink "Advanced Search"
4. Changed the filter on the left-hand side to "Done Issues"

^ You're correct, selecting "Done Issues" gives all done issues, not just those in your project. However, this is expected behaviour.

This is because when you selected "Advanced Search" you moved from the project's issue view to the main issue search page, which is not based on a specific project.

You could either:

• Not press "Advanced Search" and select "Done Issues" from the Project's Issues view's left-hand menu or...
• In "Advanced Search", modify the search to include "Done" statuses

^ Both will provide the result you're looking for. The first option is the most direct.

----------------

Scenario B:

1. Went to Projects > Selected a Project
2. On the left-hand menu, selected Issues (viewing "All Issues")
3. Pressed the hyperlink "Advanced Search"
4. Opened one of the issues
5. Pressed the browser's back button to return to the search page

For me, this behaves as expected. It returns to the search page I was on in Step 3 without an error.

I'm using Google Chrome. As a general rule, Jira doesn't run well on IE if you're using that. 

Could you provide a screenshot of what happens in Scenario B and what browser you're using?

----------------

Scenario C:

1. Went to Projects > Selected a Project
2. On the left-hand menu, selected Releases
3. Selected a Release to see its details
4. Selected "View in Issue Navigator" - to open issues in issue search
5. Opened one of the issues
6. Pressed the browser's back button to return to the search page

For me, this behaves as expected. It returns to the search page I was on in Step 4 without an error.

See Scenario B for directions here - again, a screenshot would be ideal!

----------------

Scenario D:

• Step 4 in Scenario C

I'm not sure if this is new.

The search is referencing the Project and FixVersion ID - the unique identifiers for those two fields from your Release page. This is the UID behind the names - referenced from the page entities, as opposed to manual entry into an issue search.

I checked a Server instance to compare, and it worked the same way.

----------------

If you can provide screenshots for Scenario B / Scenario C, and the browser - it'll help identify if these are Jira errors or being caused some other way :)

Ste

[Dinu Radian]

I disagree with your statement regarding what you are calling "expected behavior". Advanced Search is made available for the user to get a more comprehensive view of the items in the list. It should still refer to the selected project not to the entirety of the database. Since I am a customer of Atlassian, and not the other way around, I AM RIGHT while you my friend ARE WRONG! Besides, I reported this issues when I was surprised by the new behavior, because in the past I used the same sequence of steps, with the behavior which I described as expected.  

[Ste Wright]

Hi @Dinu Radian 

I am also a customer of Atlassian - most of us are on the Community - unless a responding user has the badge "Atlassian Team" next to their name!

Based on the steps taken - for me, this behaviour is consistent with the rest of platform. When you entered "Advanced Search" it was still filtering via the project, until you chose to utilise a filter from the left-hand menu which applies to the whole platform. This is consistent with Server (where the link is called "View all issues and filters" instead)

If you wanted to continue to filter specifically in your project using the preset filters, you're best to do so from the Issues tab without entering "Advanced Search"

But, you're welcome to disagree :). If you think your method would benefit Cloud, it might be worth raising it as a suggestion via https://jira.atlassian.com/secure/Dashboard.jspa 

Ste