Comments
-
Indeed, think of this as a two step process - upgrade and move. You can do it in either order, and plan to do them immediately one after another, but do not try to do both at the same time. I'd follow Niclas' advice and upgrade first, then move.
-
That depends on how you define "start date". The "created" date in Jira cannot be altered via the UI if you're using that, but if you are importing data from another system, most of the importers will let you set it. If you're using a custom date field, then yes, you can edit that any time. If it's a derived field of some…
-
Browse projects in *every* scheme is limited?
-
The ability to comment is controlled by the permission schemes. If anonymous users can comment, then someone has added "anyone" as a group to the comment permission. While the use of "anonymous" can speed up a JIRA, it should never be used for anything other than "browse", or you can get people making unlogged anonymous…
-
As an admin, go to admin -> manage applications and check what version of Software is installed - upgrade it to a valid version, or install it if it's not there.
-
That list is also the download links!
-
No. See the version compatibilities in the download list at https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/versions
-
The function you're using doesn't support custom fields. You'll need to use one that does (see what Jobin said)
-
You can get part of the way there - define a filter like "issues that have not been updated for 28 days and are in status open, in-progress or on-hold". Save it, and then "subscribe" to it. People who are subscribed will get a regular email listing all the matching issues. It's not quite as powerful or flexible as Jelly,…
-
Yes, that's the right place. If it's not connecting to your mailbox, or it's struggling to parse the data in the mail box, that file will contain errors (search it for the word "mail"). If there's absolutely nothing, then it's not connecting to the mail box at all, so check the server settings and that the service really…
-
Check the logs - if it's connecting and reading the mail, they will tell you why it can't import the data. If there's absolutely nothing in there, then re-check the settings, as it's not connected to the mailbox.
-
Look at the test server and check the port it is configured to run on. You can then hit http(s)://hostname:port (or even swap the host for the ip address)
-
No, you were asking how to change the base url in your TEST system - you need to change the base url on there. Joe's answer is correct, and the most detailed. When you say you "cloned" the Jira, that does mean you copied all the data to another database, which makes it independent of the production installation. I assume…
-
You've answered your own questions there Much as I complain about people using unfamiliar acronyms here, without explanations, there are some that are ubiquitous enough within the context that they generally don't need explanation. DVCS is probably an edge case - it might lose a complete new starter, but anyone with a…
-
It very much depends on how you did the merge and what went "wrong" with the data that seems to be wrong. I'm afraid this isn't really one we can help you with unless you can describe how you did the merge and the exact problems you have.
-
You have ranking enabled and schedule permission?
-
I'm afraid you're stuck then. The rank of an issue is part of the core issue data and hence you need to be able to edit the issue in order to rank it. I find the Agile docs a bit hazy on that - I can't see anything that clearly states whether you need edit either way.
-
Can the user also directly edit the issue? Go to the standard Jira issue view and look to the top left - do they have "edit" as a button on the menu bar? I'd expect "project users" to have that, but it might be more complex than that.
-
It lists the results weighted by the order I gave on the link in a previous comment. As for the criteria it puts in the url, technically, you have given it criteria. Of "match anything in this field". Not that it really matters - good code will capture urls without a full list of criteria, but it's nicer to explicitly tell…
-
Ah, yes, you've run into Atlassian's approach to searching. The search in Confluence is weighted towards personal spaces and recent updates - useful for some installations, and utterly broken for others. See https://confluence.atlassian.com/display/DOC/Ranking+of+Search+Results for that. I'm also not entirely sure I…
-
First, there's two types of date held in Jira - Date and Date/Time. They have different content, and are handled differently internally. They're actually stored in the same way (a Date is a Date/Time with the time set to 0.00) That might explain two of the differences (created/updated are working because they're date/time,…
-
Well, you can link them, but there's not a lot you get from the integration. Both systems have their own projects, users, fields, configurations etc. So the question becomes "what would you want such a link to do?"
-
Nope, the assigned-to-me gadget should show issues based purely on "assignee = current user and unresolved". It must be something else - could you have a close look at one of the issues that is missing?
-
If re-indexing fixes it, then you will want to investigate what is breaking the index.
-
The assigned-to-me gadget does exactly that - the search really is just "assignee = current user". If issues are not appearing, then they're assigned to someone else or the user does not have the permission needed to see the project, or they don't match the issue security level if that has been set. Or, possibly, the list…
-
The permissions can be complex, and the issue security layer on top does make it more confusing. I find it easier to think from the top down in this case. Start with the JIRA permissions - a user can log in, which might give them some project access. So, you look at the permission scheme. While that looks complicated, for…
-
I assume you've read the stuff about issue security levels when you say "I've read how to allow only reporter and assignee"? It's the same place as that, you can name groups in the security levels. It's generally better to use roles if you can (and put the groups in the roles), but that's a guideline, there's good cases to…
-
Do you mean the ones that are built in then?
-
What do you mean by "standard fields"? The system ones that are built into JIRA and Software?
-
Possibly, the same way you started the old one. But we don't know what you've done with the database or what the differences between the servers are that you might have to make config changes for.