Jira Next-Gen

[Shanon Macintyre]

We have a few questions around Jira Next-Gen.

1. If a project owner leaves the company and there are no other admins on the project, will a global administrator be able to view and take ownership of the project?

2. If admins are added to new projects in Next-Gen, is there a cost impact for that user role?

3. We do not want users to have the ability to invite people to projects that do not work at our company. Currently this is open, how do you lock this down?

4. Will the capability to migrate Classic projects to Next-Gen ever be available? 

[Stefan Arnold]

https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html

2. Set the password directly in the database

This is a last resort only - try the above recommended approach first.

1. You can also update the password hash stored for a user in your database. Run the following command to set the user called XXXX's password to the word sphere.

   1

   update cwd_user set credential='uQieO/1CGMUIXXftw3ynrsaYLShI+GTcPS4LdUGWbIusFvHPfUzD7CZvms6yMMvA8I7FViHVEqr6Mj4pCLKAFQ==' where user_name='XXXX';

2. Restart JIRA.

Dont know how the hash is generated, so with this you could set password of each user only to 'sphere'

[Robert Massaioli (Atlassian)]

Why do you want to do that? You might be able to reset all of their passwords instead; would that be better?