Create Issue: Not defaulting to the active project. By design or bug?

[Jason Sweet]

My team is complaining that when they click Create, the project does not default to the active project they are in, which leads to issues being added to the wrong project.  Yes, you could argue that they should pay attention but still feels like this should behave differently.

In this example, the "active" project is Operations Management. The Create issue window, however, defaults to Security Management.

Thanks for any feedback. Happy Friday!

[John Funk · Accepted solution]

Hey Jason - Here's what I have noticed with the new navigation, but I will say that I also see the same behaviors with the old navigation. 

If I am on a windows tab and change to a different project and hit Create, then it defaults to the same project that is on my screen - as intended, I would say. 

But if I am on a different tab and navigate to a project - say Project A, and then click on another tab that has Project B displayed and I click on Create in that tab, then it does indeed default to Project A not Project B which the tab I am on. 

I don't know if your users are doing that or not, but I cannot duplicate it as a problem when staying in the same tab or window. 

[Jason Sweet]

Interesting, John. I probably need to do further testing to pin down exactly how/when it happens.  Thanks for your insights here.

[John Funk]

Sounds good - let us know what it goes. 

[Jack Brickey · Accepted solution]

Hi Jason,

so I just did some brief testing on my instance and it works fine. The one thing I note here is that you are on the new navigation that is being rolled out and I am not so I have to wonder if it is related to that. I will ping others to see if they are using the new navigation and have them try. It might be worth a poke at Atlassian Support.

[Jason Sweet]

Thanks, Jack.