Comments
-
Are you trying to create issues from outside Jira (i.e. another system using REST, like JRJC) or are you doing it internally, in an add-on (App) you are writing?
-
Try running through https://scriptrunner.adaptavist.com/5.0.2/jira/escalation-service.html and let us know if you get stuck (I don't think it is particularly well written, but it does have everything you need)
-
What does the application log say the problem is? <confluence home>/logs/atlassian-confluence.log
-
Why? There's nothing I can find that would tell you to do this. Could you explain what you are trying to do? Not "connect using something" but what you are trying to achieve?
-
>Store JIRA installation and home directories in SAN storage which is mounted to JIRA app server No! Do not do that. It will appear to work for relatively small low use Jira systems but will fail at scale. It's arguable for the installation directory, but there are parts of the home directory that you absolutely do not…
-
Sprints do not belong to projects, they're created by boards. The list of possible sprints is created by the sprints that are from boards that might include the issue.
-
So you're not an administrator (you would have a config cog at the top right hand corner if you were), and you do not have the "create space" permission. You need to talk to your administrators to get yourself added to the "create space" permission.
-
I'd still want to read the logs to see what the underlying problem is.
-
Yes. A drop-down would suit you the best here, as you can give it a fixed list of options, the users would not be able to add to that list (only admins can)
-
The same principles apply on Cloud, Server and DC, custom fields work the same way in all of them (although the layout is different) You can pick a context for a project when creating or changing the data field.
-
Ah, ok, that's a field added by Software to enable some functions to work in the background. You can ignore it
-
You can't move an issue in a post-function - the issue will go into a completely broken state because you are altering structural data about it while it is being changed. Move your code to somewhere where the issue is not in a state of flux. Also, try not doing this. Moving an issue is not a trivial thing - your code…
-
The other transitions are listed in italics in the text view of the workflow because they are shared transitions. That type of transition can only be edited from the diagram view of the workflow (or the raw xml)
-
You can create as many spaces as you need, just by using "create space". You have to be an administrator, or in a group that an admin has given "can create space" permission to.
-
Please don't use option 2 - the database is not designed or built for reporting and that way lies madness.
-
It sounds like you might have a damaged configuration file - the text you are getting looks a bit wrong (especially as it appears to be pointing to a jira database instead of a bitbucket one). Could you check what your config file looks like? <bitbucket home>/shared/bitbucket.properties
-
Remove the first post-function that sets the resolution. You already have the screen that lets the users select, it's just that one post-function that is over-writing what they select.
-
I managed to miss half of these while counting down, but reading them all in one go just now has made me laugh a lot! Thanks @Thomas Schlegel
-
Which field are you asking about?
-
What did you put in the input box for the location of the file you want to attach from your machine?
-
I am afraid you might not be in the right place. This is a place to talk about Atlassian software, so unless Catalist is based on Atlassian software, I don't think we can help you much, as we don't know it (although it sounds quite interesting to me as a bibliophile, so I am going to have a look at it) My guess is that…
-
I can see this place from my front door - http://www.irvinsteaandcoffee.com/ and I've worked my way through all of their offerings.
-
Add-ons must be licensed at the highest tier of application you have (Confluence only has one application, Jira has three)
-
See https://www.atlassian.com/licensing/confluence - you need a 16-25 licence if you have 20 users on Cloud.
-
I'm afraid you pretty much have to replicate the rules Jira uses internally. Use the global permission manager to get a list of which groups are named for "use core", "use software", and "use Service Desk", then list all the users in the relevant groups, discarding any flagged as inactive. Roles and projects are irrelevant…
-
No. Your add-on licence must be at the same level as, or higher than, the highest tier of application you have. I f you only have Core, then yes, it is a simple 1:1 - 50 Core users means you have to buy add-ons for 50 users. If you have Software and/or Service Desk, then you need the highest level. For example, if you have…
-
It won't appear for the group by report because it's nonsense for a free text field. Each value in a free text field is expected to be different, so all you would get is a group with 1 line for every issue. If your information is logically group-able, then you've used the wrong type of field to capture it.
-
You will need to find or write code to do this. I would use scriptrunner to write a scripted field that pulls out the initial assignee.
-
The short answer is essentially "no". Confluence is located on one url and that's what you set the base url to. It will work if you arrive by other routes, but you will find parts of it fail and a lot of the links within it will take you to the base url. There's no way to have it run (properly) on an ip address and…
-
We can't. We're a community of end-users of Atlassian software. We have less access to your system than you do. You will need to talk to your administrators.