Comments
-
Click "configure" to the right of the option you want to add the sub-options to.
-
Ah, great, one of your administrators has destroyed the default settings. You'll need to get them to repair them, ensuring that they bring in status.
-
The upgrade has probably stripped it from your <install>/conf/server.xml There should be a line like <Context path="/confluence" docBase="../confluence" I expect you'll find the path is missing
-
Yes, you could throw the two of them into a comment loop if you're not careful! JIRA doesn't "know" that an incoming email might be from an automated response, so both ends will treat any incomign email as an update...
-
That suggests your database user credentials are ok, but the user has no access to the confluence database, or it does not exist.
-
As the clauses work independently, there are only two reasons that joining them with an "and" would get you no results other than done. The index is broken in an interesting way, or the intersecting result set really does contain no issues other than done ones.
-
Is this a Service Desk project? And are you an Agent?
-
No, stop, there's no "install" to do. You already have Core - it's running beneath Software. You just need to add an evaluation licence!
-
Right, there's clearly two more differences, although I suspect they're both generated by the same data. Look at the workflow section and the collaborators section - the new issue has more workflow options and you are named in it. A common configuration in JIRA is to say "only people matching a rule can transition issues…
-
System administration rights (it's a global permission)
-
Those differences are what we need to be looking at, that is why I'm asking for an accurate answer, not an assumed one. A screenshot of both would be of help in avoiding assumptions. That way, we can look at the actual differences instead of relying on you to spot them.
-
Yes, that's the point of having (up to) three applications in one place! Your Core evaluation licence for 10 users will allow up to 10 people to be "just" Core users. Your Software users will not see much change, as their licences include access to most Core functions. A word of warning though - when the evaluation…
-
Not without rewriting the code that handles the generation of IDs (it's a simple increment on the last number in the database), and all the code that expects to retrieve filters by their id I'm not sure that it is particularly useful change - the id is a background thing, the filter name is there to be indicative of what…
-
You can export the issues for a sprint very easily, but I suspect you want more than just a list of issues. You'll need to explain what you want from "describing details about every projects inside Jira"
-
Do you not get the "restore defaults" when you pop the Columns list in the navigator?
-
No. They are not. Please, look at all the differences between the clone and original.
-
Second sentence in my answer.
-
The marketplace is the best place to look. I'd always start with ScriptRunner (as the most powerful, and I've got a load of ScriptRunner experts on hand), but you might find Jira Misc Workflow Extensions, Automation or other scripting tools and even add-ons that provide just the conditions you need.
-
Ok, let's run over the other stuff Does the user have any special characters in name, id, email, etc? Does the user have "create" permission in any project? What are the differences between this account and one that works?
-
The installation process will ask you for connection details.
-
Created date? Comments? History? Status? Sprint? All indentical?
-
Yes, using the global header/footer and custom css options, or the similar options in the space and pages.
-
The enviornment in which the build is running does not have an execution path that includes your maven installation. In other words, your "set maven path to system environment varaible in server" has not been done correctly
-
Ok, good, so you're not entering your username, just the password into the "websudo" box. What happens when you click "confirm"
-
Restrictions are almost always based on some data on the issue. Can you tell us all the differences between two issues (one that you can log work on and one you can't). I don't believe you will have two issues that differ only by sequence number.
-
Try the one in the docs?
-
Ok, two things next: Can you test a query for the date range alone? Does that find the issues with resolutions? Can you try re-indexing projects X, Y and Z, then retry the original query?
-
That suggests you simply don't have any issues with resolutions other than "done" in those three projects resolved in July.
-
You haven't gone through a transition that has either the screen or post-function you have added. I suspect you may not have configured the workflow correctly, configured the project to use it, or you've forgotton to publish the draft
-
That does not sound like it is the admin "websudo" pop up screen. That screen does NOT ask for a user name, only a password. Could you explain exactly what you are seeing?