Comments
-
Nope, didn't see the follow-up before I wrote the last answer. Repairing a mess is a good reason to move things though, with the eventual aim of shutting down A. I think having slightly different workflows is the only real answer here.
-
You do not need to upgrade the system, a licence bought now will work for all versions of Jira from 4.0 to the current one. If you do upgrade the system, the costs are down to the work your admins will do to move it through the newer versions, plus questions and troubleshooting with users. You really really should upgrade…
-
You need to create the account with an email address. Allocate it one.
-
That's part of a shutdown, after the system has failed. What does the application log say the problem is? (Jira home/log/atlassian-jira.log)
-
I can't see the logs. What do they see at the point of crash?
-
You'll need to edit it in whatever user system you are using for your Atlassian applications. Get in touch with your administrators to ask where the users are being held, you need to edit it there.
-
That's good, it means no harm done! I don't think Next-gen projects support full CSV imports yet - you have to stick to the non-custom things that they arrive with when created.
-
You can disable the Core projects system add-on. But I'd strongly recommend just training your admins not to use those project types.
-
Check if anything was created, and if it was, edit it, to ensure it is mostly valid. Then check the application log to see what the error was. <Jira home>/log/atlassian-jira.log
-
>The issue needs to be moved to PROJECT-B This is usually a broken process in Jira terms. Issues should generally not move between projects. When they do, it should be because you're doing things like closing an old project but keeping some stuff open, or because a mistake was made and the issue went into the wrong project…
-
You probably want to start at https://www.atlassian.com/enterprise/data-center
-
You'll need to edit it in whatever user system you are using for your Atlassian applications.
-
That's a core built-in function, you'll need a "type 1" plugin, or changes to the main code if you want to override it. I'd recommend not doing that. Write a "type 2" plugin that provides an extra REST endpoint to do what you need, and leave the main code alone. You'll find it easier to write, support and upgrade.
-
There is no login.asp in Jira, it's not an .asp based application. Try just http://localhost:8080 as Fazila says - it should take you to the right login screen.
-
Software is an application that adds to Core, not a separate server. The installers are a little confusing because they're just called Jira Core, Jira Software and Jira Service Desk - the names do not tell you that they are really Jira Core, Jira Core + Software, and Jira Core + Service Desk. The licences are a little…
-
It sounds like your workplace is not reading Jira when it needs to. I don't use whatever this workplace is, so I can't really help you with it, beyond telling you what the problem looks like.
-
No, you are trying to buy software, so you need to order a licence and pay for it. Orders is one of the options at the top of the screen.
-
This is your Tomcat server throwing back data instead of sending the page data. It's obviously getting something from Jira, but not processing it correctly. This isn't a Jira problem really, its in whatever you are doing in the "redirect". Ideally, you should probably do a complete redirect - the server at…
-
I suspect something might be wrong with your email system. Jira has no knowledge or understanding of email aliases - it simply fires the email off to the address its been given. If you're getting emails from it ok on the old address, then it's able to send, so it must be the aliasing on the email server.
-
In the "orders" part.
-
Ok, you'll need to use the details you find in your my.atlassian account.
-
I'm afraid you can't. Jira only puts fields with "edit" functionality on transition screens (if you looked at the code for fields, you'd see most have a .vm for view and another .vm file for edit). Scripted fields don't accept input, and have no code for Jira to use when in edit mode!
-
Moving an issue from one sprint to the next does not touch any time you have logged on it. The time logs move with the issue. Best practice for sprints is to do what the software does automatically - moves unfinished issues into the next sprint as the old one closes.
-
No. It is the limit is there to stop people overloading - going much over 1000 will impact the performance.
-
You don't. It is deliberately locked down on Cloud to avoid people overloading your system. You will have to do what it says in that document - download in blocks of 1,000. Or, better, examine why you are trying to download an amount of issues and do whatever it is in a better way.
-
What "ID"? You pay the bills via your my.atlassian account. I suspect you mean something else though - could you explain further about what you're trying to do?
-
It looks like you are pasting in something in a character set that is not recognised by the system. You might be able to make it work by installing extra fonts on the server, but that only works in some cases.
-
You will have to edit the comments. It's nothing to do with the attachments themselves, your users have put urls in as part of the comment.
-
How are you identifying internal issues in the data?
-
It sounds like your web site is not re-reading Jira issue data when it needs to. To fix "an error in your projects", you should start by telling us what the error is.