Comments
-
In Cloud, you no longer have user ids, so there's nothing to change. Do you mean you have a Jira login on Server and you want to change that? Go to Admin -> Users and change the ID there.
-
It will "reflect" when you refresh the page.
-
It's easiest to think of Software and Service Desk licences as including a Core licence. If a user is using a Software licence, they have access to the Software functions and Core, without needing a separate Core licence.
-
Yes, you can. But that is a generalisation - you're going to need to read the framework and look at Service Desk functions in detail to see if there's a close match.
-
You are going to need some code to do the calculation and set the field. You can easily do this with Scriptrunner or an equivalent.
-
Most of the system fields can be set with issue.set<id of field>()
-
You are going to need a scripted field to do that calculation, not just import it.
-
In cases like this, it usually means that the user is used to legacy systems that do things really badly, and are struggling with systems that do it a bit better. Atlassian's bug reporting is still weak though. What they really want is people with legitimate bugs to report them, after checking that they are not going to…
-
Yes. Cloud and Server are diverging, but at the moment (and I think for a long time forward), this approach to user management won't change.
-
It's a bit old, but the principles in the main answer haven't changed! (In fact, they've not changed since Jira 3.6, which is older than the answer)
-
I think you need to start with an explanation of WSJF?
-
See https://community.atlassian.com/t5/Jira-questions/How-do-I-add-a-user-and-allow-them-access-to-only-one-project/qaq-p/253905
-
@Jim Orr Let me start with the basics: You're right. And I apologise to both you and @Andriy Tatchyn My response to Andriy was terse and short. I'll try to explain why: I'd tried to get Andriy pointed in the right direction by saying "look at the project admin rights". That is, exactly as you say, very short and can be…
-
ALexis is right - to do SSL "in" Jira, there's only one place to do it - the Tomcat that is running Jira. Anything else requires more software and a proxy server is in fact easier and faster than doing in the Tomcat, and can be a LOT more user-friendly. But you still need more software to provide the transport. There are…
-
This is usually caused by running it as the wrong user, then restarting it as the right one. When run as the wrong user, that user takes ownership of some of the files, rendering the correct user unable to read/write them. Stop the system, correct the ownership and restart it as the right user.
-
Ah, you've run into a honking great bug in Jira. This is something that only affects admins, it can easily be avoided, and has a well-documented and solid work-around. It's also quite a pain to fix in the code, and things are gradually moving away from doing it all this way, so you can imagine why Atlassian have it as a…
-
Yes, many times, but they all depend on whatever the user directory, SSO and networking systems are.
-
It should be in the urls it is trying to hit.
-
Hard to say without more detail on the issue and what is different about it compared with an issue that is showing.
-
Most of it. You could create an empty Jira server of exactly the same version as the one you have lost, make sure it works with an empty MS-SQL database (i.e. get it running and log in as the new admin to test it). Shut it down, restore the database, restart it, and re-index. You'll need to think about re-integrating your…
-
The only time I've seen this is when the client has browser plugins breaking things. You definitely need to get the results of "same user using a standard browser on another machine" and if that fails, then "different user using that browser on another machine" - you need to establish if it's that browser, machine, or…
-
No problem, I mentioned the permissions as the general "use roles" can be of some help in some cases, and "keep it simple" applies to every area, not just permissions. If you can't use "anonymous access" because of the nature of your system, then you can't - it's not something I would push if there's any decent business or…
-
No, you're utterly wrong again. I can't find people complaining about not being able to get a list that they can't use for bulk operations because it tries to tell them all the options outside the context of the the issues they need to work with. I'm not "committed to the present design", I'm trying to understand what…
-
They're in your my.atlassian.com account - check under "orders" to begin with.
-
It is possible, but it's extra work, as you'll have to integrate that into your SSO as well as the applications, and then your users will have to land there, log in, and click over to another system. It is easier just to tell your users "just log into the one you need now, SSO will kick in when you click through to one of…
-
The data exported from 3.x is in no way compatible with Cloud. You are going to have to upgrade it to at least 5.1. However, the higher you can go before migrating, the better. I'd recommend going past 5.1, to at least 6.0 (after 6.0 there's no huge benefit in going to the latest version - Cloud is effectively based on 6.x)
-
>that does not give you administrator privileges into the project, which it should. Oh no no no, board rights should absolutely NEVER give you project rights. That blows a hole straight through all concepts of ownership and security in projects. Imagine you have a project called X, which I, as a customer of your IT…
-
This looks like there is something wrong with the code in the gadget. You'll need to talk to the gadget authors.
-
Log into my.atlassian.com and look under "orders"
-
Spam? Don't be so silly. It is an answer to your question. It's not my fault you don't understand it and/or don't like it. There is nothing wrong with the archiving, it's working fine. It's something you're doing to look at it.