Comments
-
I would go from 5.2 to 6.4 to 7.0 then 7.target. https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html is a good starting doc
-
This is about inactivity of your administrators. I doubt anybody has done anything to cause this, it usually happens because someone forgets to do something. The problem is simply that your account has expired. Cloud is a subscription service, which needs regular payments. If those are stopped, or (as is much more likely…
-
I'm afraid you do need an app to help you with this. Jira has a little bit of automation built into it (more is being added to Cloud), but nothing that will do field manipulation to this level. So you need an App. I'd use Scriptrunner of course, as I work for and with people who know it. There are a couple of other tools…
-
When you changed the project type, did the issue type scheme change? Does the current one include anuy sub-task types?
-
What scripting add-on are you trying to use to do this?
-
Workflow schemes are the only way to tell a project what workflow to use for its issue types.
-
Either your mail server is configured to ignore attempts to connect from that server from that account, or there's something different about the connection in outlook. The only time I've seen that (which wasn't outlook, it was another mail client), the user had a name and a password which included some unusual European…
-
If you are using Atlassian accounts for login, then you will need to ask the owner of the account to go to id.atlassian.com to change it. If you are using your own directory (SAML etc) or Google accounts, you will need to change the email address in that system.
-
Sorry, I should have pointed at this in the answer - https://confluence.atlassian.com/jirakb/jira-ui-shows-unreadable-text-on-captcha-and-some-gadgets-due-to-missing-fonts-941590036.html
-
Ok, so whatever your process is in Waldur, it's failing to even start Confluence. I'd check the <confluence install>/logs/catalina.out to see if there's a problem there. If that doesn't exist, then Waldur isn't even trying to start your installation of Confluence and you'll need to debug that (it's not an Atlassian…
-
The original question was about Cloud, but most of what I said still stands. Upgrade through the given steps. Your licence is a separate question - yes you can jump to 250 users, before or after upgrade (the licence will work from Jira 4.0 through to 7.latest, and I suspect 8.x as well, when that is out, although I've not…
-
Hmm. I honestly don't know. It's starting to sound like the documentation is wrong. What version of Jira are you using and which doc did you get the quote from? (I recognise it, so my doubt is now old doc vs newer Jira or old doc vs cloud Jira)
-
It will be in <confluence home>/log - the main application log is atlassian-confluence.log
-
Sorry, I should have given you more - the +ok is good, but the login test is to tell it username and password. As a simple and very old standard, the command line makes you work a bit harder than some other servers. Enter user <your username> pass <your password for it> This should tell you more about what is going wrong
-
Ok, let me rephrase this a bit: * Workflows are global objects. * A workflow scheme is a configuration item that says "For this type of issue, use that workflow" - it can be* a list of every single issue type in your system, * just a single "use this workflow for all issue types" (which is the most common type of workflow…
-
I'm afraid there is not - Jira's attachment system is a flat "here's a pile of files"
-
You'll need to look at the error message you have when you try to "access" Confluence and probably take it to your Confluence administrators. We're end users of Atlassian software here, and we have less access to your system than you do.
-
> Is "Improvement" a standard JIRA issue type or a custom type? Both! It's created by a couple of the project templates. But not Kanban, which is why you were missing it in there. You do need to get the spelling right for it when adding it, the Bugzilla importer does match on the full spelling. I don't think the importer…
-
I'm afraid you have to create a classic project and then use bulk-edit to move the issues into it from the next-gen project.
-
Do you have "Improvement" issue type in the project's issue type scheme?
-
Does it let you log in ok as well?
-
Could be the wrong details, but it could also be that your mail server only accepts connections for that username from certain machines or ranges of IP addresses. If you're sure the username and password are correct, I would be checking the host name of the email server and port next. A quick test is to go on to the Jira…
-
No, it's not a bug. It's the way Kanban boards work. Kanban uses the fix version to indicate that something is "done" - you put it into a version (release), and so the board believes it to be done, so it no longer needs to display it. In the Kanban board configuration, you can change this to another filter, but the release…
-
Free, not that I know of. I'd use Scriptrunner as the most flexible option for scripting and calculated fields, but I have experts on tap, so I'm biased.
-
Those are not Confluence logs. We need to see the Confluence logs to debug a Confluence failure.
-
What does going to the localhost address get you? If it still fails, what do the logs say?
-
I've not found anything to do this (although the data can be extracted from the history). This is mainly because you don't use estimates and logs for this in Scrum - you measure work done to complete an issue.
-
Schemes are global configuration items that you select for projects. Selecting a different scheme for a project does not change any schemes, it just means the project now uses a different scheme to know how to behave. Schemes are many:1 - a scheme can be used by many projects, but a project always uses 1 scheme per area…
-
I don't believe there's any function for pulling those out of Tempo into BigPicture (as they're planning only issues as well) - you have to know what issues you have configured as internal in Tempo, then name them explicitly in filters.
-
Hmm. That mostly looks right, but we need to check the rest of the config. Have you set your Jira's connector location to /servicedesk, and the base url to support.palmsecsolutions.com/servicedesk ?