Comments
-
On the issue that should be a sub-task, Look in the options menu for "convert to sub-task", it will ask you what parent you want it under.
-
You said description in the question. Anyway, no. Summary cannot be made optional. It's used a lot in the Jira UI to inform humans, leaving it blank is not possible. You'll find some stuff that tries to pre-fill it with generated (and hence usually meaningless to users), but I can't recommend it, having seen so many Jira…
-
You don't need any scripts. The only fields that are mandatory in Jira are a handful that are structural (issue type, project) and the summary. Description is optional, until you make it mandatory in the field configuration scheme. Get your admins to make it optional in the scheme.
-
Start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
Those errors almost always happen on shutting down, rather than starting up. Although they're a bit of a pain, we're more interested in the server start process. Was there much in atlassian-confluence.log?
-
You've said "localhost" - I assume you are running the browser on the same machine that Jira is running on? If not, then it won't work. Localhost is always "this machine" (There's no place like 127.0.0.1). If you're trying to access Jira remotely, then try the ip address of the server it is running on instead of localhost.
-
That's a proxy server essentially saying "I asked Confluence, but it didn't want to talk to me". The proxy logs might tell you the basics (no response, or got rubbish), but you should start with the application logs. Look for <confluence home>/logs/atlassian-confluence.log first - that will usually have errors in it to…
-
If you use three workflows by issue type, you don't need any add-ons. If you have ScriptRunner, there is a "fast track transition". With that, you can tell it "all issues are created in status X, but if user is in role A, immediately transition to Y, and if they're in role B, go to Z" (Lazy coding, I left role C as a…
-
No. NEVER touch the files while Jira is running. You MUST stop it first. If you are having disk space warnings, then this directory is probably only one of several you should be looking at. In many cases, if you clear it, Jira will simply re-create most or all of the stuff you cleared, because it needs it while running, so…
-
I'm asking you to remove it because I think it is the cause of the problem. You need to remove it, check to see if you still have the problem. If it goes away, you will need to look into whatever this "template" is in more detail because that's the cause. If you have the same problem without any template, then it's…
-
Yes, if you have trust issues with your administrators, your only option is another Jira. Especially if a user has any access to the database - that renders all your permissions and schemes completely worthless, as they'll be able to see anything they want. I tend to agree with @Bastian Stehmann on the thing about trust.…
-
What do the logs say the problem is? <jira home>/logs/atlassian-jira.log is the first place to start, and then <jira install>/log/catalina.out if the application log doesn't tell you.
-
Yes, they can. You have to be able to trust that they won't (or don't care about the secrets)
-
An admin can always bypass all of this (without database access. You should never give anyone any database access, it's almost always the wrong answer) Admins can change security schemes, let themselves into the various levels and turn off the audit log if they want. You have to trust the admins.
-
The integrity checker is built for finding and fixing these, amongst other things (Admin -> System -> Integrity check I think. But use the admin search if I'm wrong) With ScriptRunner, there may be several things that you need to fix on your broken issues, the integrity check should handle them all for you.
-
Project can't be null, so you can just filter for "" to get all projects. Project in (xxx, yyy, zzz) is probably more useful, as most of us have projects and don't want to include all of them.
-
I'd strongly recommend treating both processes as separately. Plan and test them independently, even if you're going to do them on the same day, and don't get their parts mixed up. It does not matter if you migrate 5.8.5 to a new server and then upgrade it to 5.14, then 6.x, or you upgrade first and then migrate.
-
No, the create transition only has one end point. If you were to use different issue types for each of the roles though, you could have different workflows for each type, and hence different landing points for "create" (even if the rest of the workflow is the same)
-
The simple answer is "yes, when Jira is offline". However, there is a reason you are asking this, and I suspect that you're not going to gain anything that you want from clearing the directory. Could you explain why you asked this question?
-
Ah, I missed the number thing first time round. Some gadgets only work with specific types of field - essentially ones that hold lists. Those gadgets won't pick up numbers, dates or text.
-
I suspect someone has misdirected you. This is a community of end-users of Atlassian software. You probably need to make this ticket in your support system, not here.
-
Try removing the "template", whatever that is.
-
You'll need to explain what this has to do with Jira.
-
I'm afraid export/import is the only option
-
Yes, you can, you can just pretend the DC install is a server.
-
You will need to buy a new Cloud system with the new name, then you probably want to export the data from the old one and import the whole site in the new one.
-
A space admin can see them by going to the space tools. If you just want to check your user has access without looking though, just get them to try to create a new page in the space - if they can create pages, they have create/edit in the space.
-
Does the user have create/edit in the space permissions?
-
You can do that, but I was suggesting that you put the clause into the swimlane definition.
-
As long as you have another user with admin rights, you should be fine. Unless the old admin set up anything to run as them. There's usually little or no need for that, so I wouldn't expect to see it, and even if they did do that, it will only stop that one process working, and it'll be easy to spot.