Comments
-
What has a query got to do with this? Even if a query is the answer you need (which it might be in a roundabout way), what do you want the query to do?
-
Have a different status for "rejected", and drop it from the columns, so it is unmapped.
-
Please see the answer to your previous question at https://answers.atlassian.com/questions/46798458
-
It's an export of AD data intended for importing users into other AD systems. It dumps out a user into a block of text that can be used to recreate the full entry (groups, properties etc). How you export it depends on your AD system though - I vaguely remember a really old support call I raised with Atlassian and being…
-
Most people will write them on their own machine, and then upload them. Are you on Cloud or Server? That determines the type of add-on you need to write.
-
Write an add-on that can insert the link.
-
You need to include them in a group that has the "can log in" global permission. I suspect you've run into the "default settings problem". The default in Confluence (and similarly in JIRA for that matter) is to have a group called confluence-users. This group has "can log in", which is absolutely fine, but then the (bad)…
-
Create a standard normal user, then don't put them in any groups or space permissions that give them any access other than reading pages.
-
But the issue navigator doesn't work on a project, it works on all issues the user can see. So it can't support "reduce list to project available" because there's no way of knowing when the user might add, update or remove a project related clause.
-
And before you say "there's 746 and the list is too long", yes, that's the whole reason there's a search and roll-up - it's unmanagable for the humans as a flat list. I suspect it could be improved, but I'm not sure how. With 746 other fields, then the only useful answer is that you're going to have to train your users to…
-
Scroll down...
-
Yes, add the custom fields from the "select fields" list under "choose fields to display" menu option under tools.
-
I'm afraid you can't change it on Cloud, it's one of the restricted functions. I don't think you'll be able to get it done either, but if you really want to try, raise a request with support at https://support.atlassian.com
-
The scripts should be run as the JIRA user, yes, so that JIRA runs as that user. Do not run it as root. The first tip I'd suggest is "upgrade". Version 3.12 is unsupported, archaic, and insecure.
-
Yes, Atlassian support would be a good idea here.
-
You would need to poke the right events into the history to do that. The only way to do that on Cloud would be to export the whole system, add the events to the XML (correctly, which is not easy) and re-import the issues with their new histories!
-
It's simple - the last time a plugin was "used" was the last time JIRA was running. The question doesn't actually make any sense for many add-ons. If it's providing a field for example, then as long as there's data for one or more issues, it's in use. There are some add-ons for which you could say things like "this…
-
As a new user, use the "sign up" links (assuming your admin has enabled it) As an admin, click "user management" and then "add user"
-
I think you're going to need to look at the log and tell us more of the actual error. I'd also edit the workflow and check exactly what function is being used to do the "xxx of the issue will be cleared" - it's probably the Jira Suite one, but it might not be! Most importantly, check that the field is actually valid for…
-
I suspect you were using the card and deck macros from the Composition add-on or possibly Navitabs
-
This is a little difficult to help you with. If you can't get to your Jira, you need to fix your network so that you can, whether you change ports or amend the firewall/ But we can't tell you a lot more than that. We don't know what you've configured or why it's not working, because you haven't really told us enough to…
-
Michael has given you the link to the SQL, but it is absolutely critical that you understand the full process. You absolutely must: * Stop JIRA * Take a full backup of the database * Apply your SQL * Restart JIRA * Re-index it Never never never write to an active JIRA database - in many cases, you'll be lucky and just end…
-
Yes, I know Atlassian are working on this. I'm not an insider though, so I can't give you dates.
-
Now there's something I don't know. In older versions of JIRA, yes, deleting a project and then reusing its key worked fine. But I don't think more recent versions of JIRA let you do this. BUT, I have not tried it, so I am not sure.
-
You are correct, JIRA will not reuse dead issue IDs It's actually a bit of a pain when systems do - I've been in a situation a couple of times where a document or comment has said "see issue x-123" and when you visit it, you find out it's nothing to do with the problem because the number has been recycled for something…
-
For what? I said you could use either (or both) Yes, a group-picker is a custom field type.
-
Either would do it. I'd be tempted to create a simple group-picker field for this, and then think about scripting it so that when an issue is created, the field is set to the group for the team (it would need to make assumptions if the reporter is in more than one of the groups you're interested in)
-
What errors are you getting? Have you got in touch with Atlassian support about this?
-
If your "answers" are short, you could use a simple select-list for them, possibly backed up with some simple documentation if people need details. Or even resolutions. The temptation for me to add "let me google that for you" and "PEBKAC" to resolution lists is very strong some days, but I don't think that's what you're…
-
They must have, or the issue would not be shown in the search result!