Comments
-
Funny how? I'm just pointing out that the choice of program that your machine makes to open a specific file type depends on what you've told it to do.
-
Make sure your browser understands it should open excel files in excel.
-
I'm not sure I understand what you have done here. Have you installed Confluence yourself? Or is it a Confluence installation that you need to administrate but do not yet have the rights for? Can you log into it at all?
-
Please read the answer you have been given. Asking the same question again, when you already have an answer, does not add a lot to the conversation.
-
No, because you'd need to add somewhere to store the information, and some code in the core of the "complete" function to pop the window for the user. You can't add the code required to do the second into Cloud
-
Ok, go ahead and debug it! I'm afraid you've given us precisely nothing to work with here. What does "debug an issue" mean? Problem with one of the issues in JIRA? A problem with JIRA itself? An issue with something else that is logged in JIRA?
-
Have you definitely got JIRA Software (not just JIRA Core?), and it is enabled in the application management section? Although, I suspect the most likely culprit is that your account is not in a group licenced and enabled for JIRA Software - check the groups.
-
Edit the workflow, going in to find the transition from "ready to review" back to "in progress". Add a condition to it - probably you want one that says "Only JIRA Admins can do this"
-
The server. Jira simply runs on a system, and if it needs to reach out to other systems like AD, it will ask the server for network information. The failure here is that the remote server doesn't seem to always respond, so it's the networking on the local server, the network or the AD server.
-
The only other thing it could be is a network issue - Jira is unable to reach the AD server (and the other one that always works has a better network setup) Yes, you can connect as many Jiras as you need to AD.
-
That's quite clear - Jira is trying to authenticate and your AD server is not letting it in. You should probably start by looking at the AD server logs - find out why it's refusing to let Jira in.
-
Yes, that's the right document, the REST functions do work on Cloud.
-
It can be done - the version the SDK spins up accepts Connect plugins. What has happened here is an attempt to install a Connect plugin on a local installation, rtather than a cloud or cloud dev instance.
-
You're not doing anything wrong, other than trying to install a Connect plugin on a Server version. Connect plugins only work on Cloud/OnDemand so far.
-
Ah, thanksThere's not a lot you can do. Confluence requires unique page names within a space (and actually, this is far better for humans too, in most cases).If you were not using Cloud, you could have a look at "Scroll Versions" which sort of enables it (it's a trick, but to the end user, it looks exactly like "page with…
-
What do you mean by "maps"?
-
Saved filters based on the name may break, but users will be able to fix them next time they use them.
-
Not for Cloud, no. See https://confluence.atlassian.com/cloud/restricted-functions-in-atlassian-cloud-apps-744721664.html and the request to add the function for Cloud at https://jira.atlassian.com/browse/AOD-2636
-
Kewl. There is some documentation on Apache Velocity's site at http://velocity.apache.org/, but the layout of the site is awful and it's dreadful to try to find anything useful, and even then, there's no obvious examples or human-friendly guides. The closest I've found to anything readable is…
-
You have not got a custom field of type "assignee", I suspect you mean "user picker"? (Assignee is a system field, you can't add more) Anyway, your code is fetching the content of a custom field. In most cases, this will be an object, which you then need to question further to get a human description instead of a…
-
No. Cloud has it's own directory, you can't use others with it.
-
Andre covered my questions about the field. However, have you also enabled the permission? The field needs to be on the screen and covered by field configs etc, but the user creating/editing the issue also *must* have the set-security permission, or the field will be hidden (same way you "lose" assignee or reporter if the…
-
As many as your database lets you put in a field. Effectively, it's unlimited.
-
Could you please re-read what Thiago and I said before. The answer to your first "SS" question is given in those. And again below in the method to protect the field. * Create a screen with just "sprint" on it. * In your workflow, create new transitions that go back to the same status (e.g open -> open, in-progress ->…
-
No. Jira does not do field level permissions. Thiago's solution moves the "edit" of a field into the workflow, it does not affect the create issue step or change the way the field works or is offered to users. If you did it that way, you would create the issue without the sprint field and then have a "Change sprint" link…
-
No - there's no SMTP server in JIRA, it just connects to the server you tell it to to send email. The problem you are having here is purely to do with the SSL setup on your mail server and what Tomcat or Java (i.e. not JIRA) are doing with the certificates you have provided for them. It's quite likely that you've run into…
-
Why: https://confluence.atlassian.com/jirakb/jira-timesheet-reports-and-gadgets-removal-from-jira-cloud-792504481.html I don't think this was a good move by Atlassian - I understand the move to Connect, but to remove functionality like that is a little unfair (they could also have implemented a temporary change to the…
-
They would need to add them into the group or groups named as JIRA or System adminstrators. This is a global admin setting though, and we always strongly recommend only having a small close team of JIRA admins.
-
That's the problem with re-packing - you've probably missed some settings in the config of the WAR. But there's no way to know what you've missed.You could spend weeks working this out, it would be far easier to migrate to an installed version.
-
It's because it's a WAR version - the installers can only upgrade a standard setup of JIRA. You'll either need to unpack and rebuild the WAR from a clean install of a new JIRA, or migrate the 6.3.12 to an installed version that you can then upgrade.