Comments
-
You need to add transitions that go to other "done" status, then they will appear on the screen. You can get rid of the screen by cutting it down to one transition to done status.
-
The SQL exception is the main culprit. It means Jira can't connect to the database, so there's no chance of it starting up. It worries me that you say the "native Jira DBMS" - there is no native one, but I guess you mean the embedded one (it's an off-the-shelf file and memory based, called H2). This is scary because it can…
-
All of those are "request types". You could simply name the types as you have in your question, but it might work better to have a different portal for each group (so, an account portal, a software portal and so-on)
-
Move is controlled by "move issue" in the project you are in, and you also need "create issue" in the target project when it's different. Change parent simply needs the user to have edit permissions in the current project. If you're not seeing "change parent", then either you don't have edit, or you're looking at an…
-
The main advantage would be having everything in one place.
-
Yes, they're separate systems, each user will need an account on each system. If you replicated though, that would not be necessary. Sam could edit on one end, and the changes would be copied over to the other end without him needing an account there.
-
And a page on Cloud would not be in the same system as the Server one. You'd need to find a way to synchronise two separate pages.
-
Yes, there are two "database custom fields" in the marketplace I've used which both allow you to build field contents from other databases, and there may be more. Well worth a look!
-
I don't think even Behaviours (part of Scriptrunner) can get into the display at that depth. You could default the value and do the validation on create/transition with Behaviours and Scripts, but limiting the calender would require dedicated code I think.
-
You say you're already logging time, so you must have set something up already. Jira does not have sub-projects, so we're going to have to ask what you have set up so far. At what level are you using Jira's projects?
-
You're right, Columbus shouldn't care if another domain is failing. Does vandala only exist in Columbus? Also, can you try getting the lines of logs above and below the line you gave in the question (only 5 either side at most)
-
I've used rewrites instead of redirects, as I never quite got the redirect correct. I'm using the below instead of your Redirect line, one up from the bottom of your posted code RewriteEngine on RewriteCond %{SERVER_NAME} =atlassian-test RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
-
No, the assignee field is a system field which uses the user directory directly, it's hard-wired as a core function in Jira. You could make the assignee redundant (hide it in all field config schemes), and use another field that can connect to an external database, but that field would not see the contents as "users" the…
-
No. What makes you ask?
-
Did you create the home directory and permission it correctly?
-
Start with maybe https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html
-
Right, so you've got Crowd as a user directory, and it can't connect to it. You'll need to go to Crowd and add your new Confluence to it so it allows authentication.
-
The free version is installed on Cloud automatically, but you now have to ask for it to be enabled.
-
That suggests a failure in the authentication system (user directory). What does the application log file say the problem is? <confluence home>/logs/atlassian-confluence.log
-
Ah, I see, I totally misunderstood the description of the problem. What do you get in the "visual" tab under the description?
-
Two things: 1. You say "We were also charging data directly into the database via a script" NO. Stop doing that now, and ideally go back to a backup you took before you started doing. It does not work, you will break your system. Never never never run database changes to a Jira database while it is running, and generally,…
-
I'm sorry, I was not clear when I asked. I do not know what you mean by "test steps" or "test details". Are they fields? Sub tasks? etc
-
Ok, great, so how do you define "empty"? Or "not empty"?
-
How are you defining tests? What add-on is it? (Or is it just issues?)
-
I'd say you were in the role of developer in the project.
-
So, the question becomes: what are you doing differently to the instructions? As other people are using them and getting working systems, we have to question what's different about your process.
-
Could you explain this "time to resolution"? There is one built into Jira, but it does not "start" anything, it's calculated from data on the issues, so I suspect you're talking about something else.
-
Go to project admin and have a look at the permission scheme. I suspect it says "Add attachments - only admins", and you'll want to open that up a bit more.
-
Is Software licenced and active? Check under Admin -> Applications.
-
Are you trying to re-create the old server on a new machine? Or are you setting up a new machine with an upgraded version? Is this a full move, or are you wanting to merge some of the projects from the old server on to an existing Jira?