Comments
-
The problem is that because JIRA supports many types of user directory, it has a very simple approach to groups - it uses the group name as the key. It used to do this with users too, until VERY recently (logon = key in that case), and it's a nightmare to refactor the whole system to use a key instead of the group name.…
-
Premier support is not a daily offering. I would suggest that you contact a partner/expert instead of Atlassian, and don't just ask for a bit of support on the day - you'll want to involve them in all your planning and testing if you want them to be able to properly support your upgrade run.
-
First, sanity check on the groups. Go to Admin -> Global Permissions and take note of the groups listed under "Jira administrators", "Jira System Administrators" and "Jira Users" (it's usually just "jira administrators" and "jira-users", but it's worth checking). Those three lines determine who can log in. Then, the simple…
-
Is the account still there when you look in user management? If it is, is it enabled and in the "can log in" group? (usually jira-users)
-
Use the issue links to do that.
-
No, the Epics are containers for issues.
-
Try giving it the number of seconds - that's how it exports it, and what it stores in the background.
-
All JIRA 6.x have CSV imports available to the administrators.
-
Didn't get what? Sorry, I'm curious.
-
I think you meant to ask this on https://answers.atlassian.com/questions/33157874 ? But even if you did, I'm not sure the question makes sense. What support are you talking about and what is a "rundown time"?
-
Do not "hide" the field. Remove the timetracking field from create and edit screens, but leave it on view. Then use Stephen's answer for workflow properties to block the users from logging work
-
Ah, I see, the issue is with the ranged band of page numbers (I have no idea if this area has an official name). My apologies - the screenshot in the question was so small on this screen, I didn't really see it.I have a feeling that although the display of 4 then ... is a variable, it's set in the source code, not as a…
-
I'm afraid "number of pages in issue navigator" does not make sense to me - could you explain what you mean by that?My guess is that you are looking at the display where it says something like "page 3 of 7". If I am right about what you're talking about, then "need to change number of pages" is nonsense - in my example,…
-
Use the account recovery options, links at the bottom of the login screen
-
Yes, the SQL in there is unreadable as well. Can you tell us what the simple "show us active users" does as compared with "show all users"?
-
Correct, they do not support any (ab)use of the database. Your use of "as" confuses the query and I can't read it clearly enough to see what it's doing (I know as is useful, but plain SQL without it is far more readable when you're trying to work out what a query is doing, as it remains more like the way a human would…
-
No. You need POP or IMAP to provide an "inbox". SMTP is for transferring mail, it is NOT an inbox and cannot be used for receiving mail. To use snail-mail as an example, in the real world, a human writes a letter (the body of an email), puts a name and address on it (the email address), and gives it to someone to deliver…
-
Good start, but you need to test the whole connection. Ping tests a port and a service, and only really tests the route and that the server is running with something that responds to ping. You're using a totally different service - mail. So, you need to test that. Ask your Exchange administrators for the port number they…
-
That means your JIRA server cannot get a connection to the mail server. Check the network allows the connection, that the mail server is running on the server and ports given, and that your credentials are correct.
-
Move it into a status that has the "jira.issue.editable" property enabled in the workflow (and think about adding the "can't comment" one too). You can see an example if you look at the "closed" status in the JIRA default workflow (the uneditable one distributed by default) There's actually quite a few of these properties,…
-
Yes and no. SOAP is deprecated in favour of REST in later versions of Jira. But it's not been removed yet, so it should continue to work. The API has not changed a lot (if at all), so if a SOAP call works in 4.2, it's probably going to function in the same way in 5.2. But there's no way to guarantee that in every case. The…
-
It does not make a lot of difference if you hide the fields.
-
No. To change status, you use a transition. That's the end of the story. You can do things like automate it - have a look at the "Jira Toolkit" and "Auto Transition Listener". It won't do what you specifiy here, but it's the right idea. I'd reach for the script runner though - you can write listeners in that, and it's got…
-
Duplicate of https://answers.atlassian.com/questions/210452/redirect-the-existing-on-demand-confluence-uri
-
Yup. See https://confluence.atlassian.com/adminjiraserver070/advanced-workflow-configuration-749383189.html and look for opsbar-transitions in it. I think you can set it to 0 to turn the menu off, but if not, then setting it to a silly high number you'll never reach works fine too.
-
How are you associating issues with a client? A good starting point would be to create a filter to find all the issues based on that, and save it. Then you can start looking at reporting on it (issue navigator for example)
-
The advice still stands. You need to change all the assignees to someone who is going to remain in the system. The status of the issues is utterly irrelevant - Jira needs a valid user account in reporter and assignee. Generally though, the advice is not to delete Jira users at all. Remove them from all roles and groups,…
-
You'll need to write an add-on to do this - one that can give you your button and then pop the applet up. As you mention it's for the dashboard, I'd recommend writing a gadget to do it.
-
For info on why Atlassian doesn't do it, and hence why the plugin was written, see https://jira.atlassian.com/browse/jra-1330
-
No problem. It's ok when it's one people are more familiar with, but there are hundreds now, and most of us don't know them when the tags are simple like that.Hopefully, someone from the vendor is monitoring that tag and will pick up this question soon. In the mean time, my partial answer is1. The vendor has said 5.6, so…