Comments
-
This functionality is coming into Server versions. I don't know if any of it will make it into Cloud.
-
Correct. Plain Jira considers versions to be completely project objects. A version in one project has nothing to do with one in another, even if the name is identical. Portfolio layers some linkage and commonality across those.
-
I'm confused now. Do you have an issue you cannot transition after it was added? What does the permission helper tell you about that? Now if you bulk edit, and select that single same issue, can you transition it?
-
This isn't going to work the way you are thinking. Filters find issues. They have nothing to say about how they are then presented to the user (slight exception - the "order by" clause is used in a handful of places). There is no group-by in the filters, because that's formatting, not results. You will need to think about…
-
No, I asked what you see when you visit the existing profile for peterm, not the other one, or what happens when you create - you've told us that already.
-
To create a version, you have to have project administration rights (and/or a kanban board "release"). Check the permissions of the two sets of users.
-
That's actually slightly better - it means the transition is failing cleanly early on, rather than getting part way through and breaking your data. On the down side, it stops is diagnosing anything on the front end!
-
This can happen when the connect plugin has failed (as per Conor's docs), or if you're trying to install a Connect add-on in a Server system.
-
Hmm, hard to tell without the log. You'll need to talk to Atlassian support direct, on https://support.atlassian.com/contact Does the issue history (not activity) tab show any updates when one of these transitions fails?
-
What does the permission helper tell you?
-
If the permission helper says "no permission", and you've not got transitions going out, then that points squarely at transition conditions, not validators (validators happen after you start a transition, conditions block them appearing at all)
-
I don't understand what a ponumber or amount is - one of them is not a word and the other has nothing to do with field config. You need to create a new field configuration, and then a new field configuration scheme (to tell different projects to use the new field configuration)
-
Yes, I think you are missing something, but I think it's Jira-speak, rather than what you're doing. Jira Software effectively has three layers: * Epic * Standard issue types (usually Stories, Bugs, Improvements, Issues, but often Tasks, Projects, Paperwork, Meetings etc) * Sub-tasks (Technical task, sub-task, sometimes…
-
To write a "script", you will need an add-on to provide the scripting hooks and engine. So yes, whatever way you're doing this, you are going to need add-ons. Warren's answer below is an all-or-nothing - if flag a field as mandatory, it is mandatory from the point of issue creation.
-
You need validators that can check the entry is correct. The Jira ones that come off the shelf cannot do this. You will need add-ons to provide them. (Some that do it might be free, but you need add-ons)
-
Most places I've worked have holiday, sickness, meetings and "other reason I'm not developing" issues in projects separate from the actual work trackers. Adaptavist have holidays and sickness separate, but the range of "development" work generally means we consider some meetings to be part of it, and we have projects for…
-
You don't, the UI has no way to do it.
-
What have you done differently to the documentation, and what are the problems you are seeing?
-
No. There is no point in being able to search for things a user cannot see. If they can find things (even if they can't see the pages initially), then that's leaking the information that is restricted, so you might as well forget restrictions and open it up to them so the search works because they can see it. I suspect…
-
The command "whoami" will tell you about your login. The "apt-get install jq" means it wants to install a JSON parsing tool on the system you are running on. Problem is that your system does not have that package in its current repository lists. You'll need to read up on how to add a repository for it to your particular…
-
I suspect there is only one link here. Links in Jira are vectors, so you can form a sentence like "issue X depends on issue Y" and "Issue Y is depended on by issue X" - that is the same link, but directional. Off the shelf, Jira ships with one link type which has the same label on both directions, so "X relates to Y" comes…
-
No! Please read ALL of the upgrade documentation.
-
Ah, you said Kanban board, which only exist in Software. The Core boards are not Kanban, and are not configurable. The only way I can think of doing this is to have an "active" project and an "inactive" one. When an issue becomes active, you'll have to move it.
-
Go to Board -> Configure Board -> Columns where the columns are defined.
-
No, because a status can only exist as part of a workflow. If you had one hanging "outside", you'd have no way to get the issues into the main flow. But you don't need anything like this. A workflow that's inactive -> to do -> in progress -> done is fine. You just tell your boards to only look at the three active status.
-
The most simple way to do this would be to have a "not active" status in the workflow, which you drop from the active boards. Then have another board (or probably more usefully, just a saved filter) that fetches all the inactive ones and allows you to move them to an active status. You could do something similar with a…
-
Yes, from memory, it's 3,000, or "roughly 15 times what most humans can usefully parse on a board". A board really should not have more than a couple of hundred. If you've got thousands of issues, that's fine, but split them up into usefully sized boards.
-
You can if your licence ends after the release date of the version you want to go to. Start at https://confluence.atlassian.com/doc/upgrading-confluence-4578.html
-
There is the cascading select list custom field type, but beyond that, no, you need code or add-ons to join fields like that. The Behaviours module in the Script Runner add-on for example.
-
No, you'd notify the group when anyone is assigned to it. You'd need code to do it by user.