Comments
-
Mmm, they can't - the incorrect function is thrown by the OS trying to start something that isn't there. It's not getting as far as running anything Atlassian have written. I'm not sure what the installer has done, but you shouldn't need to change the path - they should be set to use the bundled version.
-
Er, I have no way of knowing what your compiler is configured to do on your machine. I don't even know what you're using, as you haven't said.
-
I already explained what happens when a non-logged-in user arrives. SSO twists it a little bit, but not that much. All that happens with SSO is that a user will be logged in automatically IF they have already logged into another SSO enabled application AND they have a Confluence account.
-
Your compiler will create either a .jar or an .obr - that's what you need to upload.
-
The base url lands them on the dashboard, which typically contains a login section. You can change that, and have just the dashboard, or even a home page. Of course, they might be following a link into something that is not the dashboard, but they won't be asked to log in directly. The option to log in will lurk in the…
-
>I looked up post-function but couldn't made use of it Look for the "set field" post-function. It's standard, so you don't need add-ons.
-
The context is the contents of the environment in which your code is running. If you are running a post-function, then the environment contains "issue" (the current issue you are transitioning), so you can just use that. If you are running it on a project screen, you won't have an issue, but the project will be available.…
-
Random questions asking about bits of the process are not the best way to learn about this. It's not amazingly complex, but read Atlassian's documentation first, rather than ask us to parrot out the responses to questions you could have got there (both of your questions are answered there). If you have further questions or…
-
Admin -> manage add-ons -> upload add-on Although, if you were using the SDK in full, the atlas-run script would download, install, run and add your add-on to a dev system. There's also a script for installing your dev add-ons to other systems, but I've not done it enough to find it useful.
-
You can upgrade to any version released before the end of your licence. It is not something you can do inside the application though - you need to download the new version and run the installer, telling it to upgrade an existing system.
-
This is a known problem with JIRA (although it's not actually JIRA's fault). In some cases, the issue data becomes mismatched with the workflow data. JIRA can't work out what transitions to show, so it does what you describe. Changing the workflow fixes it because it goes back over all the affected issues. The other fix is…
-
No, that's utterly wrong. Please re-read the first two lines of the answer.
-
Yes. That screen is what you get when you click "create linked issue". It is the "create" screen for the project and issue type you select. So, You need to revise the fields on the "create" screen for the project/issuetype you are trying to create the issue in.
-
I don't think it's a bug to be honest, it's more a structural thing in that they've moved on and actively dropped support.
-
It's a bit more sensitive to proxy misconfiguration in JIRA 7 - what did you add for scheme, proxy and port on the end of the connector?
-
It's your xyz.atlassian.net
-
Ok, so this is an add-on. The question is about the context of where the code runs. If, for example, it's a post-function, you are given the "issue" object for the issue being transitioned. So, where is the code running? What is the context?
-
Correct, you can't hack the code files you'd need to change.
-
Yes, they do backups, but not the ones you are trying to download. The problem with your scrip is that it is not logging in correctly.
-
JQL gives you a list of issues, noting more. It has nothing to do with displaying data from the issues. You'll need to think of a way to get the data you want out of whereever you are using the filter. A standard answer is to use one of the add-ons that provides "last comment" as a scripted field - you can simply add it to…
-
Most Atlassian Solution Partners are expert at that sort of migration - have a look for an appropriate one at https://www.atlassian.com/partners/search?page=1
-
There's a whole pile of problems in here, but I'll try to keep it simple: JIRA Service Desk does not exist for JIRA 4.3 JSD provides some custom field types, but most are held in the core of JIRA, so unless you wanted to amend one of the SD fields, you're actually looking in the right place, as I'm guessing you really are…
-
getId() instead of getKey() will work. But it sounds like you have a context problem too - where exactly are you trying to run this code?
-
Possibly, although I think it's not an easy read. https://confluence.atlassian.com/adminjiraserver072/enabling-public-signup-and-captcha-828787685.html#EnablingpublicsignupandCAPTCHA-EnablingpublicsignupforJIRAServiceDesk I think you may have enabled public signup for all users, which gets them into JIRA as users, and you…
-
As I said already, the "create linked" screen uses the screen you have set up for the project and issue type you are trying to use the function to create. You need to revise the fields on the "create" screen for the project/issuetype you are trying to create the issue in.
-
issue.getProjectObject().getKey() is working for me - returns the key of the project as a string
-
That document works for me, so no. And, again, we can't tell you the settings directly, your accounts may be different to the ones other people use
-
You will need a little bit of code to put in a "condition" - it should be able to look at Task1 and return "false" if it is incomplete, which will remove the option to use the transition on task2. There are a load of add-ons in the marketplace that can provide that code, or a way to implement your own version of it.
-
It looks like there is something wrong with their account in your Active Directory.
-
My guess is that you are not resolving the issues. For an issue to be resolved, you must set a resolution. Even if you don't want to use it, you need to set (and clear) the resolution, or all sorts of things in JIRA don't work properly. * Look at your workflow * Decide which transitions go from an "open" status to a…