Comments
-
On point 3, you need to give them "create issue" as well as "browse project" On your questions 1. Actually, dump point 2, don't put them in a group. Instead, change your permission scheme to say "create = role: user (or something)" then you can place different users into the role in different projects. 2. Not really,…
-
Mmm, the 2008 install we've got in another team here doesn't use roles at all. They've granted the five rights I mentioned to their Jira user and it's working fine. They have not granted sys-schema type rights at all. Your error message still clearly states your problem was "don't have SELECT" as well, nothing more.
-
Probably overkill, all you needed was to make sure it had insert, select, delete, update and index.
-
I'm not sure how the "roles" work in SQL server, but the Jira user needs to be able to select, insert, update, delete and index at the very least. Your error message says that whatever you've done, the Jira user does not have select rights. It cannot read the tables. You need to fix that.
-
Um, your error message explicitly states that your user does not have the right permissions in the database.
-
Your database access is set up incorrectly. The user you are using does not have "select" access on the database. You'll need to fix all the "grants" the user has and restart the app.
-
1. You should use whatever database is best supported and understood within your organisation. Given a free choice, then MySQL definitely. But the most important thing is how well you can support the database internally. 2. Where you connect from is not really that important. You can run Jira on different servers and…
-
A security scheme defines a set of levels that can be applied to an issue. Each level is a set of rules that say who can see the issue with that level. To set a security level on an issue, a user must * Have the permission to edit the issue * Have the permission to set issue security * Be covered by the rule that defines…
-
In the "security scheme"
-
Unfortunately, the answers you've been given so far only work for one very specific situation - they do NOT set the security level, they set the assignee to one person and then rely on the default security scheme in the project to do things like "hide the issue from everyone except that person". If that's what you need to…
-
I've not run into problems going 6.0 to 6.4 directly. There's usually been things with add-ons, but the core data (meaning JIRA, Agile, Service Desk and Portfolio) tended to go smoothly. The only hiccups I've had with them were having to re-install Agile to make it load properly.
-
Pretty much what I'd have said too
-
Indeed, you need to take assign out of the loop basically. As you say, the ugly fix is to remove "assignee" from all screens where you can change it. That forces the users to use the "assign" option, and hence trigger the required message.
-
Less of a "bug" than a long-standing design failure in Jira - it only fires one event per change. That means it can't handle "reassign as part of an edit/transition" because it's firing the "change" event. There are a swathe of "please fix this" type issues logged with Atlassian specifically for this problem, but they've…
-
You can edit a simplified workflow in the same way you would edit a normal workflow. But I wouldn't recommend it. If someone re-organises the columns, you can easily lose some or all of the changes you've made. I've also had an issue with a post-function which worked on a normal workflow and failed on a simplified one, but…
-
That is the way it is intended to work. If you want to change that, your options are to hack the core code that does this, or educate your users to right click and open in new tab. Hackery ( NOT recommended ) is athttps://confluence.atlassian.com/plugins/servlet/mobile#content/view/300813780
-
I'd hope Sean can ignore this discussion too. I'd like him to expand on the requirements so that he can get an improved answer that can fit his needs. But until we have more requirements, the answer remains a bad one. Period.
-
It most certainly is a sales pitch. You're trying to sell a product or service. In itself, that would really not be a problem, if it were an appropriate option. You can not know that it is appropriate.
-
It just seems like you simply don't grasp that a sales pitch is not the right answer. I can't put it any more plainly.Virtually none of the answers in this forum are sales pitches - they offer alternatives, they ask the questioner to think through what they're doing, and most importantly, do not offer limited selections of…
-
It just seems like you have not bothered to read what I've said. I apologise if you have, but you just keep trying to justify a sales pitch as an answer when it's not a good one, and my whole point is that. You've made no argument that counters that.I'm more than happy to stop. My point is clear, and you are the only one…
-
Please re-read what I have said, and stop blustering.Whether I have used it or not is irrelevant. I'm not bashing the software at all. Note the use of the word "potentially", that is critical.For the umpteenth time, you DO NOT HAVE ENOUGH INFORMATION to begin to select a solution. So all solutions are potentially awful.…
-
Please re-read what I have said. Whether I've used the software or Appfusions stuff or not is irrelevant.You do not have enough information to suggest a solution. So an answer that tries to sell one solution is a bad answer. Because at this point you do not have enough information. I can't see anything in what you've said…
-
All your essays say that you should want the best for your customers. I completely agree with that.Which leads me back to the fact that a sales pitch for a potentially awful solution is a bad answer. It's not a case of me not understanding that your answer is "valid". It might be, it might not, you can't know that. You're…
-
So you agree that your answer is a bad one because it is a sales pitch and not actually useful.Glad it has finally got through to you.
-
Ok, let me explain in plain simple English:Your Q&A is:Q: I have Jira, I want to do requirements and votingA: Here's one single product that I am sellingLet me put this another way:Q: I want a red car with a radioBad answer from an Audi salesman: Buy my Audi Good answer from someone who wants the best for the customer: Ok,…
-
<sigh> You really don't understand it do you?All I'm saying is that trying to sell a specific solution when you have no idea what the actual needs are is the wrong approach.Your own essay here directly supports that - if you have a field in which you don't really know what you want, then saying "my product can do it" is…
-
But the question doesn't say any of that. It has a couple of requirements, and they're met by JIRA already.My question tries to get at why the question is being asked in that way - there's probably more requirements to come, but we don't know that. We're certainly NOT in a position to even begin to suggest solutions - we…
-
Why not just use JIRA off-the-shelf? You can use an issue type of "feature request" and it has a basic voting system built in. Everything you've got so far can be done without any 3rd party stuff at all. (Heck, it's how Atlassian themselves handle it). So maybe if you expanded on the reasons you think you would not want to…
-
Um, actually, no, it won't work. The short answer is that there is no way to associate two workflows with one issue type. What you can do (and I think you already kind of got this), is branch at a workflow level. You have a single workflow that allows two routes, and it never really converges. I.e. an issue is created, the…
-
Um, they asked about Confluence...