Comments
-
I don't know. That statement works, but it looks like you've changed the rights for the user and broken them. I don't know what you've changed.
-
No, the Core board definition is fixed in the code, you can't change the 14 days without hacking the code behind it.
-
You don't appear to be giving it an issue to transtion.
-
No. Export what? What are the lines in the export?
-
Ok, that's a post-function then, but because it's a change of status, it won't work. You need to use an automatic transition, as the create issue process needs to finish before you start the next transition. It looks like you are using "Script Runner", which does have a "fast track transition". Rather than try to write…
-
You can do some of this if you install an "issue picker" custom field type. Be warned that those fields are known to have usability and performance issues, and are less functional that "issue links", which are the better way to refer to other issues.
-
What do you mean by "export"? What are you trying to report on here?
-
The location depends on when you want this to happen. Do you need it as part of the workflow? If it's for a specific transition (e.g. move from open to in-progress), then you need to do it in a post-function If you need to run it every time a field is changed, you need to do it in a listener.
-
Check that the missing field is not already included in the result as the list of fields won't list ones already there. If that's not the issue, check that it has a "searcher" (admin -> custom fields -> your field -> edit).
-
1) Yes, that's pretty much it - the right-hand column matters. 2) I don't understand what "it won't select" means. The settings on the rest of it seem good, I just don't grasp the problem 3) Are the issues they complete a) being put in the far-right column, and b) having time estimates?
-
You will need to find or write some code that can do those calls, as there's nothing in JIRA that you can use to do them. Obviously, it'll need to go into an add-on, or you could use one of the add-ons that allows coding inside JIRA. It's not really a JIRA question itself, but I've done it by following the basics in…
-
Is customfield_1234 really the custom field numbered 1234? Go to Admin -> Issues -> Fields, look for the one named customfield_1234 and hover the cursor over one of the edit options. Does the url that appears on hovering say id=1234 in it?
-
Log in as an admin, go to the service desk configuration in the project to see how the field is set up, and follow that to the list of options.
-
Please, re-read the first sentence of my answer.
-
Right, "connect to" makes more sense. Use the JIRA REST API. Have a look at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis
-
If you have a resolution of "discontinued", then an administrator added it. A couple of add-ons I know will add resolutions when they are installed, so that might be inadvertent. Similarly for status if that's what is meant (it's not clear from the conversation what is happening - is it a status or a resolution being set?…
-
I understand that, it's what your code tries to do, but you need to tell us where you want to do this.
-
Last time I used SAP, it was totally opaque to source control systems, and had a model of "always roll forward" so in an ideal world, you shouldn't need one. (In real life, it's a stupid and expensive design and a very good reason for avoiding SAP)
-
Sounds like it might be easier to use a couple of custom fields to gather that data and report on it directly.
-
There is no real way to do this. And you would be breaching the terms of your contract - you are required to keep "powered by Atlassian" displayed in the footer.
-
Confluence doesn't natively track "access" to spaces, so there's nothing stored you could even begin to query. You'll need to look at one of the tracker add-ons you can get.
-
No. If you want a read-only field, you can create one, but you will need code to fill it in. The usual option here is a scripted field though - you'll still need code to do that, and most of us will use one of the scripting add-ons to do that.
-
If you mean you want to run page exports through a word template, then no, not natively. However, the Scroll Office Exporter add-on does allow you to something that's almost that.
-
Yes, that user needs full access to the database.
-
There's no field setup in JIRA that does things like that natively, but see https://community.atlassian.com/t5/JIRA-questions/How-can-i-make-one-custom-field-depend-on-another-custom-field/qaq-p/596533 for some suggestions.
-
Please, do not edit questions when you have a new one. Ask another question. You've made the correct answer look totally wrong,
-
The resolution has nothing to do with changes to the login, that's a complete red-herring. It is definitely something in your configuration too - "Discontinued" is not an off-the-shelf resolution, it's something your admins have done.
-
You need some code to do this, to tie the two fields together. You could try injecting some javascript (hard to maintain, harder to get right and a royal pain most of the time), or use an add-on that can do it. The one I know of is the "Behaviours" module in the Script Runner. There are loads of examples here in the…
-
There's two things you might mean here 1. You literally mean you want to write "code in JIRA". This is possible for Server versions of JIRA, and is a good idea to do it in Java, because that's what JIRA is written in. You write and deploy an add-on containing your code, and JIRA runs it internally. (There's also the option…
-
Not sure what you mean by "community edition", but JIRA 7.3 should accept a Cloud import. This is sounds like a problem with the importer that should go to Atlassian over at https://support.atlassian.com/contact