Hi All,
We've experienced an issue today in our Jira Cloud instance where an issue was created in the wrong project.
This was not a user issue. (Not PEBCAC).
____
The issue works like this:
1. Two projects open in the browser (Chrome) with multiple tabs and issues of each project
2. Navigate from project "A" issue to project "B" issue. Project B issue has existing "linked issues" in-situ in the issue
3. Click on "+" in Project B to add a "New issue"
4. The "Create issue" screen is presented
5. Project "A" is present in the "Project*" field and is now linking the wrong project. It should be "Project B"
____
I have a video which I'd like to load but I can't here, I've attached the screenshots.
Hi, Clinton. How are you today?
Thanks for the screenshots and for describing your scenario.
There is a open bug report for this case. Please access the bug page and click on Start watching this issues to receive all the updates about that. Please, feel free to share your thoughts about this case on that ticket comments.
Apologize us for any inconvenience this bug might cause to you and your company.
Additionally, check our bug fixing policy for more information.
Let me know if there is anything else we could help you with.
Kind regards,
JOÃO NUNES
Jira Support Team
OK.
Got it, thank you so that's bug JRACLOUD-69274 and the link is:
https://jira.atlassian.com/browse/JRACLOUD-69274
Thank you, I am now watching this bug.
Is there any reason why this is low priority, given that larger instances team members may have this issue often when working between projects?
Thank you, Clinton.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Clinton!
According to our bug fixing policy, a critical bug is - the production application down or major malfunction causing business revenue or high numbers of staff unable to perform their normal functions.
This issue we're facing is not preventing the user from creating issues or using multiple tabs to work. Although you need to ensure that you select the correct project while creating an issue.
This does not mean that the bug will not be fixed and that we do not care about that behavior, for the contrary, we're always working to make Jira a better application. But there are more crucial bugs that will be prioritized to the detriment of this one.
Let me know if that helped you.
Kind regards,
JOÃO NUNES
Jira Support Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
I have this problem, and do not agree that this issue is non-critical - I have created epics and tasks that has exposed sensitive data to customers in other projects. Using Jira for a company that adheres to ISMS, ISO27013 and GDPR, this bug is therefore critical and should be addressed at a higher level than is currently.
Thanks,
Kim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kim,
I recommend you get in touch directly with the Cloud Support Team on this. The original bug is closed, and if you're having issues right now regarding GDPR, then you'll want to be in contact with the team directly. Let me know if you have any issues raising a ticket.
Thank you for your understanding!
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.