Comments
-
Replacing the evaluation licence with a production one is trivial - log in as an admin, go to the licence page, paste the new key into it. There's no fuss, downtime or effect on users. The only thing to be aware of is number of users. The evaluation licence is unrestricted, your production one probably won't be. If you've…
-
This sounds like a good case for changing the project key, yes. It's far easier and better than creating a new project and moving the issues. Just bear in mind that you can not re-use the old project key.
-
Have your tried a different browser? What is the url you are using and what does the browser land on when it displays the malformed request message? (obscure the domain, we're only interested in the jira part of the string - e.g. if you're going to http://something.com/jira , we only want the bits from jira onwards)
-
What does the application log say the problem is? ( <jira home>/logs/atlassian-jira.log ). Are you using the right version of the add-on for your version of Jira?
-
The current version is the "most stable".
-
I'm struggling with these logs. There's no indication of which one happens at the time you attempt the install, and there's errors missing before and after the ones you are posting.
-
5.x and 6.x are not Cloud versions. 5.6 can be upgraded to 6.x easily. All 6.x releases in the main download pages are "stable" For database versions, see https://confluence.atlassian.com/doc/supported-platforms-207488198.html
-
There are no "templates", and the project setup never adds resolution to any screen. So one of your admins added it at some point!
-
That's correct. You'll need to read up on the Cloud versions documentation to see if any/all of it migrates. I've had massive problems with Tempo data in the past personally, but I don't know if it's improved. I can tell you that none of the ScriptRunner stuff can come across. Cloud doesn't support half the functionality…
-
NO NO NO! NEVER add a resolution like "unresolved", it's going to break everything. You need to edit the "create issue" screen and remove the resolution field immediately.
-
You have to give the system the full host name and location of the mail server you are trying to get mail from.
-
Ok, that makes sense. You have given it a "host name" of "mailstore", but that is not the full host name of your actual email server. Jira needs to be able to *fully* resolve the name of the email server in order to connect to it.
-
In what sense? You're going to need to explain this question properly.
-
That's not a native Jira function - which add-on are you using to provide it?
-
Where are you setting these "project variables"? What are they?
-
What documentation have you been following, and what have you done differently to what it says? Where does "it's not working" happen?
-
If you've placed the issues in two different projects, then created a board based on "project = one of the projects" then this is the correct behaviour. To get both projects on the same scrum board, edit the filter so it says "Project in (project 1, project 2)"
-
Could you explain the question? Tomcat and Apache are different things, and it is unclear what you are trying to do with Confluence.
-
I asked a couple of weeks ago, and was told that there are no plans to support EWS, as it's got the same issues as MAPI In the cases where you have to use non-useful protocols, the most simple solution is to set up your own dedicated mail server that uses standard open protocols and forward the mail via that.
-
Hmm. There should be a "Try Service Desk" box in the bottom right hand corner of the first screen-shot you gave. Does your server have full access to the internet? (Or at least marketplace.atlassian.com)
-
* Not unless you ran into significant problems where errors were occurring. * No, they do not yet offer that as a service, although again, they'll do some support, and the last summit (Barcelona 2018), they announced they have some migration code that they will be sharing soon. * Yes, they upgrade the applications…
-
The boards are based on a filter. To "add a new project to a board", you have to add the project into the board filter. (This does not apply to Cloud Core boards which are simplified, do not do sprints, and have a 1:1 relationship with a project)
-
If this were the case, then there would be a flag somewhere that flips the project type and does all the re-configuration work for you. There is not. The projects are simply Software projects, that's it. You look at them through Scrum or Kanban boards to select which way you want to work with them at the time. You can…
-
It looks to me like getRecords does not have those parameters, so it's failing.
-
No, this one was definitely about resolution. It was being set, so the gadgets that work off "resolution is set means the issue needs no more work" were hiding them.
-
Sprints are built by boards, and boards can include many projects. So, yes. The most simple example would be to have a board that uses a filter for "Project in (x, y, z)", so you get issues from all three projects and can put any of them into a sprint
-
The administrator audit log will capture some project changes. Log in as an admin, go to the admin section and use the search to find "audit"
-
Yes, try "Sprint = X" or "Sprint in (x, y, z)" type searches in the advanced search.
-
Those are not acronyms/abbreviations in use in Jira, so they must be something your administrators have set up. We can't really tell you much, as we can't know what they are!
-
Because you have not selected a project type that has sub-tasks by default. All you should need to do is add one or more sub-task types into the issue type scheme.