Comments
-
Go to the board configuration and check that the board filter includes "order by rank"
-
Did you move the jar files as per documentation?
-
They'll need to extract any data they want to migrate into a format that can be imported by Confluence and JIRA. I'm afraid I can't tell you much more than that. Migrate is a "suitcase word", good for a concept, but unless you can explain what is actually in it, there's not a lot more we can do.
-
"Best" is really difficult to answer, because Jira is flexible and hence tries to fit in with your way of working, rather than you having to adapt to the way it does things. I'd work backwards for this one. What do you want to report on? Are you going to end up requiring your users to put all their time in Jira so…
-
When you are creating an issue, the security level is not set (this is not a security risk because the data only exists on the user browser until it's committed). Once it's created, Jira is able to read the security level and see that they don't yet have the rights to be added. To me, that does sound like a bit of an issue…
-
Generally, yes. Unless you're highly familiar with it, you don't know what you might break. Code hacks are a pain on upgrade. And you are unsupported by Atlassian if you use them.
-
Jira doesn't have a lot of html, it works mostly with JSP, Velocity and Soy. You'll need to dig around in your installation to find them and edit them.
-
Sort of. This is a slightly more advanced usage, but it'll work.You could add "participant" from the Jira Toolkit as a user in the security level. Or, you can add a specific "user picker" field called something like "cc" and actively put people in there (and use it in the security scheme too)
-
You need to re-work the permissions - have a group for "can log in", and don't use it for anything else. Don't put the restricted users into roles in projects you don't want them to see, but do add them to projects you do want them to see.
-
The core of the code I think you need for the script runner is below. The id of the security level is up to you, you need to read your security scheme to find it (hover the cursor over the link to "edit" each security level in the scheme and you'll see a url that contains "id=4" ) def myFieldName = "A custom field name"def…
-
I'd use the "script runner" plugin - it'll save you all the work of creating a post function. You'll still need to write the code, but not a lot, and the script runner has lots of examples in it
-
You can do that as a "listener" instead - same basic code for the update of field, but a listener listens for events. "Edit issue" is a standard event fired when you update an issue without a status change. I tend to do a complete conversion - get the listener to pick up all events that might change the field, including…
-
That really is a terrible way to configure it - just because Jira lets you do something doesn't mean it's a good idea. This is the sort of thing I spend time removing when I get called in to sort out Jira problems. Don't use dynamic roles in security levels, it's a disaster for the users.
-
No. It's totally different. Although they share the good design principle that you don't let users create stuff they then can't see because it's utterly wrong for the way humans think and causes you massive support problems.
-
Most of us add more plugins to provide the conditions we need. I'd always install the Jira Suite Utilities first and see if that can get you closer (actually, that's a recommendation I'd make no matter what the question is - I pretty much refuse to do any work on a Jira system until it's installed. It's free, and so…
-
Ah, no, it is definitely not a bug. It is done by design, and it's the right design. In almost all security use-cases, a user should not be able to set the security level to a level that they are not in. In a small handful of cases, a user just being able to see the other security levels is a security breach in itself. On…
-
You aren't going to be able to create a plugin that does this. The security level field is built into the core of Jira, you can't replace it. Your options are to hack the core (basic advice on that is "don't") or to go around it. My previous suggestion is your best approach - create a parallel field that has all the…
-
Mmm, not really. A workflow is a process something passes through. A status is "where the issue is" and the transitions are an action that change the status. There is no "transition phase", the transition starts with a status, and ends with one, an issue is never part-way through a transition. You don't usually put…
-
Not quite, a transition can be reused, as only the end has to be in one place. So the simplest case is M number of Status with just M+1 transitions - one into each status from any or all of the other status, plus the initial "create" transition. My maths is a little rusty, but I agree that (n-1)^m +1 is the second worst…
-
No, a transition, by definition, only has one end point. What you do is create several transitions, and protect them with "Conditions". These can do things like "user is in role X", "Field Y has value Z in it", and a condition will hide a transition if the condition is not met.
-
Ugh, dynamically hiding things like that is a recipe for confusion, but I suspect you know that. The closest I can get you without code change is roughly what I described before (i.e. the one that causes 300 problems a month) - I didn't do quite this, but create a custom field with similar/same named options as your…
-
Hmm. No, and you don't want to either. On a technical level, you could do it with some code hacks. On a security basis, it's generally frowned upon - a user does not necessarily need to know that there are other levels of security and in most cases, shouldn't need to be able to use levels they don't belong to. Although…
-
Ah, I see. You don't need code change, just put the field on screen. If a user can see the issue because they match the security rules, then they will see the security level field as part of the standard display. To change it, they must have the permission to change security levels though (it won't show on edit/update…
-
Absolutely not. That would break the security, rendering the security level system utterly useless.
-
First line of the error tells you all you need to know - the email server doesn't think your user credentials are valid. You'll need to check that you've got the right settings, and if you have, look at the mail server to see why it is refusing access.
-
Probably the first. That's what you're used to and it's a sensible grouping of the work. One product per project, then one Scrum board per team - a board can cross as many projects as the team needs it too, it's not locked to a project. The one thing I'd say (having been through this transition many times), is that you…
-
That's a copy of the question Please assist with the following: In JIRA is there a way to or a plug-in("Gliffy Diagrams For JIRA" or draw.io or Creately for Jira or Confluence for Jira s/w, etc) that may support the following? - please don't create comment/question clones.
-
Install it, then use "insert gliffy diagram" to pop up the window to draw your diagram
-
Or bung them in JIRA so you've got more clever reporting and a workflow. (Actually, I'd continue with the forum idea in Confluence as it's better for fleshing out ideas, then you can use the select-right-click to create batches of JIRA issues when you're sure you've got a good task list)
-
I suspect you've run into this: https://confluence.atlassian.com/jirakb/unable-to-migrate-from-jira-5-x-to-jira-6-x-and-above-774244597.html