Comments
-
You'd need to rewrite a huge swathe of JIRA's core code (And add-ons) to do that. Where are you getting this "multiple cards on an email" from? That would be easier to modify to include the information you need.
-
Yes, you should upgrade that to JIRA 6.4, then to 7.3, then follow https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
You don't need to add anything, the property is definitely there on Server. Log in as a full admin, and go to "general configuration". Press the "advanced settings" botton near the top right. Press ctrl-f and enter "subtask". You will find one or two settings, it's obvious which one you need. Edit - another thought, if…
-
No, workflow and issue type scheme are project attributes, not issue elements, and hence they're not searchable with JQL You will need to find or write a JQL function that can get to those settings, or add a couple of custom fields which you set on the issue creation (and don't need to put on any screens)
-
No, the format of a JIRA issue key is <project key>-<sequence> The project key is a little configurable, but that's it. (I'd also advise against your format in general - it's not memorable enough for humans to find it useful)
-
Make sure the priority is on the "edit" screen for the issue type in that project.
-
Ok, not "running slow", but you suspect you are running low on memory. Problem is that the symptoms you are seeing are not typical of low memory issues. You don't know that running out of memory is causing them. Also, one of the things about memory usage is that a lot of us don't really know how to read what we see. What…
-
I don't know what you're reading, but it does not sound right. The content index takes up some space on the disk and is required for searching, it's nothing to do with speed or size. Rebuilding the index will not lose anything, it will just ensure if there are errors in the index, they will go away. "memory space running…
-
The component is a field the user is expected to fill when they create/edit the issues.
-
I guess you are on Cloud then? There's no advanced properties that mention subtask at all?
-
If this is a dashboard you created, then you just click add. If it's someone else's dashboard, then yo'll need to get them to add the gadget. Or get the admins to change the owner to you. If this is the system dashboard, then you will need to log in as an admin and go to Admin -> System dashboard
-
JQL is not SQL, it's for finding issues. It will not list components, because they're not issues. Best I can do is tell you to create and save a filter for "project = x and resolution is empty" to get the list of active issues, then add a "filter statistics" gadget to the dashboard. Tell it to use the saved filter, and…
-
Ok, well, the error message is implying that it's trying to take a backup of something, which suggests that there is data in the database, and/or pre-existing data setup in the home directory. As the user you want to use for the database, log into it and check there are no tables. While you are there, check that you have…
-
On server, there's a setting under Admin -> General -> Advanced settings. From memory (so probably not quite right), look for jira.columns.table.subtask You can add jira field keywords into that. Thinks like priority, environment, reporter, and customfield_10010
-
So this is a completely clean installation? You've done nothing more than take a completely empty database and run the bitbucket installer?
-
You'll need a bit of code to do that I'm afraid, you can't do it natively.
-
It's based on https://www.lithium.com/
-
You need to get your admins to add it to the screen (or make it optional)
-
Probably worth raising this as a suggestion over at https://jira.atlassian.com/browse/CONFSERVER
-
If the schema is empty, that answers the question. Can you confirm what you have been doing, as the previous conversation seems to contradict itself. I think what you have done is: * Installed bitbucket using one database (internal?) * Created an empty database, with the user bitbucket and run the SQL to grant it access to…
-
No. Projects, issues, fields, workflows, time logs, comments, etc - everything that is related to "issue tracking" is done in JIRA When the main product can't meet your specific needs because it's a generalised application, then you start looking at add-ons
-
Tempo's folio add-on does that doer of thing.
-
Ok, that's another way to do it. Although I would question why your add-on doesn't do the report you want.
-
Edit the workflow, click "add status", put in "Pending"
-
Click "add transition", select "link from all status". Repeat for each status.
-
Your user will have to download copies of the work logged data to mangle in Access. By far the best way to do that is to use the REST API to pull out the data they want, then write something to change it into the shape you need.Or use the functions in the add-on you have?
-
There is an "introduction" gadget available as standard. There's also a "text box" gadget that is a bit more free-format, but it is disabled by default, as it can be used to open security holes. An admin can enable that in the "manage plugins" section if you're willing to risk that. Generally though, JIRA is not a…
-
That would suggest that your JIRA system does not have the right SSL certificates installed to be able to reach the system being called in the webhook. You'll need to get the client certificates and install them in the JIRA JVM.
-
It's because the Core boards are not supposed to be a replacement for the Software boards. If you need more flexibility in the boards, Atlassian want you to look at JIRA Software (where you can use whatever queries you want)
-
No. Absolutely not. Access is not a proper database and it's pretty much impossible to use it as a back-end for JIRA. Even if you could get it to work (you won't), you are totally unsupported and won't be able to upgrade it. If you mean you want to keep JIRA on a proper supported database and then try to use Access for…