Comments
-
I've found it. You're using an old version of Jira that doesn't have the columns there. I was looking at 5.2
-
Yup, that's broken. I get icons in that section. Could you * Try another browser (IE is poor at standards and often gets stuff wrong, it's always worth checking for "IE is broken as usual") * Confirm if you've done any customisations around this area?
-
I don't understand that. Could you give us a screenshot of what you are seeing?
-
I'm curious - why do you need to differentiate between them in order to create a link between them? That might help explain why I ask the second question - where do you need to use this information? Are you coding for something? Front end javascript? Back end Java in a plugin? Something else?
-
The reporter should be an existing account (even if the user signs up for it, or sends an email to a Service Desk set up to create them automatically)
-
Yes, it's only the "see different information" that raises my hackles, because it's divisive and confusing. I'd love to see Jira support a proper model of "person matching A can raise issue types X and Y, but not Z". There's some approaches I've used in the past. I've seen more clever tricks mentioned in Answers I think,…
-
No. Schemes are by project. It's very difficult to manage a project when people see different sets of information, although it's very handy to be able to let different people enter different pieces of information. It sounds like you either need different issue types for each type of entry, or maybe you should create a…
-
Not without amending the core of Jira. The rule is not quite "must be in group", it's "user can log in", but that is effectively locked to "must be in a group that is flagged for counting as a login". I do see the logic of your scenario, I think. In Jira terms, you'd like people to have accounts with no groups, until…
-
As many as your database and server can cope with. I've seen JIRA installations with millions of issues and several thousand projects. The hardware struggles when you get to that level, but when it starts getting big, you move to JIRA Data Centre, and that can spread the load.
-
Yes, a lot of people are being quite annoyed by this direction to make every project have its own schemes. I suspect it's part of the move towards delegating more of the admin that Atlassian would probably like to do (i.e. letting the users look after their own projects). But it's a bit of a pain for admins - most of us…
-
I'd treat this merge as a separate task from the upgrade - you can do it before or after the upgrade with the same effect. (I'd be tempted to do it after, as JIRA 6 is a bit nippier than 3 so you won't be waiting around for it to do the updates for as long) I'd also completely bin the idea of "a single scheme", unless you…
-
I don't think you can customise the assign screen without amending the core code in Jira.
-
Don't shout, I have a headache
-
Yes - all issues would have to have an assignee at all times.
-
Joe's disallow unassigned issues is the easiest and probably best answer, but you could also * make it mandatory in the field config if you want to allow unassigned issues elsewhere * put validators on the workflow, so that it can't have its status changed while the assignee is empty * use a workflow property to disallow…
-
I'm afraid not. I seem to remember you could do it in old versions, but it tended to cause problems as people tried to share filters that other people couldn't see the contents of, so it didn't work. The move to group/project means you can rely on the recipient having access.
-
Which calculated/scripted field add-on are you using to do this?
-
Have a look through https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html to start with
-
Mostly, does depends on which system you're using. Most cases, you will simply add the group and five or the permission, but you will generally also nerd to remove everyone else's permission as well, of you are aiming for "only this group"
-
You need to decide how you are going to decide what the "resolution delay" is, and then report on that. The most simple one would be for a support project, where you'd simply use "created < -8h" to find ones over 8 hours old, but most people are a bit more sophisticated and do something more complex. Often, I find scripted…
-
The usual way to do this is create a filter for issues that are getting too old and subscribe to it.
-
The board is trying to follow the workflow. Nothing else on there would stop them. I think you need to show us what columns you have defined for the board, what the board filter is, your workflow diagram (or the text view) and then an exact definition of a transition that is blocked for the user (all conditions and…
-
The boards follow the workflow. If you have a columns like: * To-do, containing status "Open" * In progress, containing status "In dev" and "In test" * Done, containing status "closed" Then your users can only move from "to do" to "done" if the workflow has a transition from "Open" to "closed", AND they have "transition…
-
Your last line says it all. You need to give the user the transition issue permission in order to allow them to do any transition in the workflow. You've correctly protected the Done transition with a couple of rules, but you have not protected any of the other transitions with anything. Add a rule like "only developers"…
-
If you're still stuck here, could you give us a list of all the conditions on the "close" transition, and a look at the relevant parts of the permission scheme and user's group/role membership.
-
The conditions are the starting point for this question. You need to look at the conditions on the "close" transition and modify them or the user so that they meet the conditions. If, for example, the conditions say "only group X can do this", then the user needs to be in group X. The more standarad and useful case is…
-
It's not clear what you really want to set up to allow or prevent here, but we can try to explain some principles. There are two layers to transition permissions in JIRA. Every transition can have "conditions" added to it, and these are intended to prevent the wrong people from performing transitions (or prevent them from…
-
Yes, exactly as I said, you'll need to create something to provide the form and then post data into Jira via REST I'm guessing by "identification number", you mean "Jira issue key" - you'll need to do some coding to work out how to fetch that back from Jira via REST
-
I'm not sure what you're trying to achieve here - you could simply get your users to use "create issue" in Jira itself. If you want something outside Jira, then you'll need to write the "form", host it on a server/url somewhere and write some code behind it to post to Jira OnDemand via REST. Or, you might want to have a…
-
No, the Cloud application has to live on <something>.atlassian.net (and even moving it to a different <something> is a pain) There are requests to allow for other domains to be used, but they're moving slowly.