Comments
-
JIRA 7's implementation of applications has changed the way groups get access and changed the defaults, so a lot of docs out there are based on old information. The easy answer is that you can do whatever you want, but that's not of any use to you. Both of your suggestions are valid. I'd tend towards the first though, as…
-
Do you have any Service Desk admin groups defined?
-
You need a more clever post-function - some code to pick up when you want to run it and when not, and wrap that logic around the "assign" statement in it.
-
You don't need to worry about fields if you're doing an import (but you should install all the add-ons before import) The import is effectively an upgrade, which will take all the configuration from the 7.0 system into the 7.3, wiping out what was in the 7.3 install before. I'd question why you're doing this, when the…
-
This usually means Synchrony is failing for some reason. Try going to Admin -> Collaborative Editing and disabling Synchrony. If my guess is right, then you'll find you can use the old-style editor to edit pages fine. We'll then have to go debug what is wrong with Synchrony. If I'm wrong, then we'll need to start looking…
-
I assume you mean Issues -> Custom Fields -> Add custom field -> Advanced. If your field type is missing from there, then either your add-on has not loaded, or the atlassian-plugin.xml is incorrect, and not telling JIRA about your field type. Is your add-on displayed in the list of add-ons in Admin -> manage add-ons? If it…
-
You don't say what user directory you are using, or whether you are on cloud or server. If it's the internal server directory, log in as an admin and you will be able to edit the user's detail, including manually setting a password. If it's Cloud, then you'll need to log into the user system as a site admin. REST calls…
-
The usual reason for that is an application link warning where there's a problem communicating with the other end of the link. Because it can't talk to the other end, the warning message loops and gets nothing, hence the spinner. I managed to do exactly this on Friday, it was down to a misconfigued proxy and missing an SSL…
-
"It is not taking it" is totally useless as a response. The reply to that is simply "you're doing it wrong". Please, tell us what error(s) are you getting?
-
The "Release notes" field is not a JIRA system field, it is something your administrators have added. They can go to the "field configuration scheme" and change the field to enable rich-test editing.
-
These don't work for Business boards, from what I can see.
-
Try the below. Note it's from a 7.4 install and has a context of <server>/jira, rather than just <server> <?xml version="1.0" encoding="utf-8"?> <!-- ==================================================================================== Atlassian JIRA Standalone Edition Tomcat Configuration. See the following for more…
-
I suspect you're in the wrong place. This is a place for the Atlassian community, ETABS is not one of theirs.
-
You could include a REST call in your builds, but a better option is a Jenkins plugin. I've used https://wiki.jenkins.io/display/JENKINS/Jira+Issue+Updater+Plugin in the past, but there are a couple of others that do it
-
It doesn't, because it can't. The process of editing an attachment is: download a copy, edit it locally, upload the new version. The server cannot know what is being done to a copy of the file it holds. There are some add-ons which put a form of lock on attachments so that people can tell someone else is editing and has…
-
Ahh, the joys of https - always the right thing to do, but a pain in the neck to get it right How are you doing your SSL? Terminated at a proxy, or with JIRA and Confluence's Tomcats?
-
The tables you need are the AO_60DB71 ones for the sprint and board data, and then you'll want to be reading either customfieldvalue or work-logs combined with jiraissue for your estimation data, and customfieldvalue to identify the sprints. Trying to read the index is probably a non-starter. You can read off lucene…
-
That's mostly what the ranking field does. There's no add-ons I know of that give you a next-in-line field, or duplicate the ranking, but there are some "queue" add-ons in the marketplace that could do what you need.
-
I wouldn't start with a user picker, as you aren't going to be picking "users", just lines from a database. I'd look at the simple multi-select list. I'd actually go look at the two "database custom field" add-ons in the marketplace.
-
No, you only need to change the base url for the new system.
-
Ok, you'll need to investigate your mail server logs to find out why it is refusing the connection.
-
Ok, a migration off HP ALM is always a good move. There are a couple of options. You could look into the "connectors" in the marketplace - although they might not bring across everything you want. The other option is to write something that pushes data into JIRA over the REST interface
-
I'm stuck, I don't know what is happening, as there's only bits of log and no description of what is happening.
-
A 421 means the service is not available. My best guess is that it's not configured to accept email from your Bitbucket or Confluence servers.
-
You've enabled logging on the MS SQL Server side, and it's writing a log for everything. Confluence doesn't need that. Attachments should be in <confluence home>/attachments.
-
I think your instinct on what is going wrong is spot on. It looks like you have a custom field of type "project picker" and when the project was deleted, the data was not removed I don't think there's a fix for this without code or poking data into the database. I'd want to read out the content of customfieldvalue for that…
-
JIRA Server doesn't have boards yet. See https://jira.atlassian.com/browse/JRASERVER-45690
-
That suggests either that your server is overloaded, or it's going out to an external server and that is being slow. Are you on Cloud or Server, and what work-log related add-ons are you using?
-
Neither of them add fields to versions directly, but they do support more version management functions. ScriptRunner can help, yes, you could use it to write functions that could keep more information alongside versions - a simple implementation might be to have a project with an issue for each version in it, then you can…
-
You've now talked about three different databases, and although there are some migration tools around that might be able to convert one to another, we've had problems with them, so we don't recommend that at all. The correct approach is to run your h2 based JIRA, go to admin -> backup and restore, and run the xml exporter.…