Comments
-
I don't think you've stumbled on https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html yet. That explains questions 1 and 2 better than I can. For question 3, I can't tell you. The customisations are things you have done to your system for your reasons. And the steps for upgrade are…
-
You'll need to find or write an add-on that can provide the same functionality.
-
I'm not sure what you mean by "type of plugin". You need to find or write an add-on that you can deploy on JIRA.
-
Yes. See a related conversation with more detail over at https://community.atlassian.com/t5/JIRA-questions/Notification-Scheme/qaq-p/602039
-
Yes, just follow the steps in the second part of the doc.
-
Have a look at https://confluence.atlassian.com/adminjiraserver071/importing-data-from-csv-802592885.html
-
You've given the setup an incorrect or badly formed url when ytying to connect. We need to see that. Depending on how far through the install you've got, there are two possibilities. 1. There's a file in your JIRA home directory called dbconfig.xml which has the connection settings in it. We just need to see the connection…
-
You can just run "macroName: <macro>" in the search to get a list of pages it's used on. With SQL, you're into searching the bodycontent table text for snippets of text referring to the macro, then joining with other tables to try to establish more information about the pages.
-
No, because you already have one, sort of. JIRA and Confluence have an "embedded crowd" which provides their internal directories. The embedded crowd can't be extended or used for most other applications, but you can tell a Confluence system to use a JIRA's embedded Crowd. That's what the doc is about. If you do that with…
-
If I understand this question, what you want is that when a query is run, to tie it back to "the logged in user who caused it to happen", so you can firewall based on them. This is not going to happen because it can't work without rewriting the whole of Confluence. The database is abstracted away from the users. There are…
-
There's two types of user here, and they're handled in different ways. A JIRA user (Core, Software or Agent) sees all of JIRA and has their access controlled by their groups and roles. That's mostly done on a project level, and the usual approach is that a user in a project can see all the issues in it. A Customer does not…
-
No, there are no events for that. The audit log captures scheme changes, but there are no events. You could write a plugin to hook into the administrative stuff in a similar way to the audit log does, but I'm not sure how complex it might be.
-
As described earlier, you can not do it. You need to remove it from create and edit screens.
-
I watch the EAP release notes, and the "preparing for" for the developers. They're not 100% accurate, sometimes the content changes a bit before actual release, but they give you a good feel even if things do change. So, *…
-
No. The issues in a project take the project key. The only way you'll get that structure is to have a project for each issue type!
-
It is not quite "mandatory" in JIRA speak. The field is technically optional, but when placed on screen, it does not have an empty selection. You can't change this without code. The field should not be placed on create or edit screens, it should only be used on screens attached to transitions that go from an open status to…
-
The general intention is that you'd put JIRA Service Desk on the same JIRA you've added Software to. You can still create a link to another JIRA, it's just not automated and won't create (unless you do a bit of coding)
-
Ah, yes, the link is for creating issues in projects in the same system. It doesn't create issues on other systems.
-
I tend to rename it myself, but I was being gentle in my suggestion in case the questioner isn't ready to take the flak when the irate user starts asking why their fields are suddenly called Majikthise, Vroomfondl and Slartibartfast.
-
No, the board needs to include all the status for Scrum to work properly - note that you normally would take issues into a sprint as "new", not in-progress. There is no way around this, you have to have a column with the status in it somewhere. Also, I'm assuming your committed and in-progress status are different (not the…
-
What add-on are you using to try to do this?
-
There are add-ons which provide functions that do "create another issue" as post-functions. I'd use the script-runner, as I've almost always got it to hand, but there are others in the marketplace that do it.
-
Edit the issue. It may be that your edit screen is missing the version field. It might be hidden by your preferences (check the cog at the top right), but if it's not just hidden, you'll need an admin to add it to the screen.
-
No. Forget the database, you don't want to touch it. You will need the names of the fields you want the REST call to fill in. You can get those by just looking at the "create issue" screen.
-
The "fully open" view of an issue is its "view" screen. Issues also have "Create" and "Edit" screens associated with them. These screens can contain no, some or all custom fields. You can find them ny going to project admin and drilling down through the "issue type screen scheme" One other point though - custom fields have…
-
Get an admin to add you to one of the groups that grant administrator rights.
-
You'll need to write a little code to do this. Your web pages will need to be able to use JIRA's REST API to create issues, and ask JIRA for issue information to display.
-
If it happens again, then try clearing the browser cache.
-
Yes, in the past. There are three main things that happen 1. Each add-on you have chews up a little memory permanently, even if it's disabled. When they're active, they all cause the JVM to use more resources, as they're doing more than plain JIRA does. The effect of that can be negligble, but in some cases when an add-on…
-
That's up to you really. You appear not to want to track them in your dashboards and sprints, so I'd keep them separate and put them in a different project. Or use an issue type you exclude from your board and sprint.