Why can I login to a deleted account?

[boardtc]

When you go to login there is this annoying feature that pops up in the top right hand corner asking if you want to login with google :-(

I made the mistake of clicking on this and it created a new account. I added my comment before realising it was a new account. I then edited the commend to say "delete this comment" and I deleted the account.

Then when I go back to login it automatically logins me into the deleted account and I can;t find a a way to login to my own account on my default browser. I am using another browser for this.

So I have the following comments with the annoying I'm New here:

How is it possible to login to a deleted account?

[Dave Meyer]

@JD Lobue for JSW and JSM you can do this in two ways:

1. For company-managed projects, you would change the permission scheme that a given project is using to grant the "Browse Project" permission to the role you created, and remove whichever other entities you might not want to be able to have access to the project.

2. If you created the role in the team-managed project, then anyone with this role implicitly has access to the project.

As far as I know, there is not a way to manage access to Confluence spaces based on a Jira role. You would need to use a group.

[JD Lobue]

Hi Dav, Thank you for this. Is there any way to limit based on a custom field? In other words I only want users in that role to be able to see work depicted by a value in that field. 

[Dave Meyer]

Hey @JD Lobue ,

I’m not entirely sure what you mean. My best interpretation is that you’re asking if you can only allow users in a certain role to see a given field on an issue.

This idea of “field-level visibility” isn’t supported in Jira and likely never will be. The most common way to work around this is to maintain two distinct Jira projects, one that is “internal” with a certain set of fields, and a separate project with an “external” set of fields. There are also several “issue syncing” apps on the Atlassian Marketplace that can help with this.

[JD Lobue]

No. That is not what I'm trying to do. What I'm trying to do is limit issues to only those that have certain values in a custom field based on a role so that X role only could see issues that had a custom field set to Y and no others.

[Nic Brough -Adaptavist-]

You can't do that with custom fields, but you can with issue security.

This lets you set a "level" on an issue that limits visibility further than the project's "browse" permission, you can set up levels to allow totally different sets of people to see issues.