Comments
-
True, there's no swimlane by group because you're supposed to be working together on common tasks. Breakdown of work by user/group is more likely to be done either at an assignee level or by having different boards for different groups. For an "overall filter", there's the quick filters.
-
I'm afraid core boards are never going to be like that, and Atlassian might well resist anyone writing add-ons that do it. Because they would want you to get Jira Software to provide the more powerful boards.
-
My instinct is to check the permissions in the target project(s) - I think you will find you do not have "create issue" in them.
-
It really is as simple as: Click on "Space Tools" then "Permissions" The admin icons are to the left (Server and Cloud) when you're in the space, and immediately give you "permissions" as a link, which takes you to a screen listing all current users and groups with access, and there are "edit" buttons on it. There's really…
-
No, you can't, natively. You will need one of the add-ons that can (conditionally) transition to a second status after the initial creation.
-
One of the space administrators can add them.
-
Yes, the field appears under details because it's not caught by other panels. If you didn't have it on the screen though, it would not appear at all! Start developing at https://developer.atlassian.com/server/jira/platform/getting-started/
-
Most of the default setups have the assignee as a field on the screen already, so you can set it. If it's missing, just add it to the "create" screen, but bear in mind it will only appear for users who have "assign issue to other people" permissions in the project.
-
Ouch. I'm afraid you will need brute-force. Stop Confluence, log into the server and go to <confluence home>. Search the sub-directories in there for the add-on's files, and move them all to somewhere safe, remembering to preserve notes on their directory names (some will be the installation, others caches, but it's worth…
-
Check the permissions in Jira for the project. You need to have "create issue" for it to appear in the list (remember that admin rights mean admin, not do-everything)
-
If you could do it with configuration, I would have said so. The issue view is divided into several panels. When the screen is drawn, each panel selects the type of fields it has to display and pulls them out of the list. So * Dates and times are in the date panel * Users and groups in the user panel * Time tracking in the…
-
Admin -> Issues -> Resolutions
-
Correct, the view screen arranges things in a particular way. You would need an add-on that provides a new web-fragment that is a panel that contains a copy of your field, and supresses it from the main display of custom fields.
-
You will need to write code to move a custom field out into its own panel.
-
That request is just for Priority schemes for projects, not individual issue types.
-
Those are too long to be useful as options in a drop-down. You will need to shorten them to a useful string. (Note that the fact I couldn't tell them apart without having to concentrate means they're useless to your humans as well as being too long - you will get inaccurate reports if you try to use them)
-
There is no easy answer for this, because there are two ways a project might be using a screen. The first one is complex, but can be queried with a bit of work. The relationship is Project -> Issue type screen scheme -> screen scheme -> screen The second one is harder to query. The relationship is Project -> workflow…
-
It depends on what has expired. If it's a dev or evaluation licence, yes, it might be, as a lot of the API goes read-only. If it's a full commercial licence, it won't be a problem
-
7.3.7 doesn't have the new issue view option
-
"connect timed out" is the smoking gun - it cannot connect to the database over your network, or the database is not running, or it has been configured to not allow the connection from your Bitbucket server. Check that the database is reachable with psql on the bitbucket server - that should give you more detail on the…
-
At it's heart, it is an issue tracker - software built to handle lists of things that need doing and organising getting them done. It is heavily aimed at developers of software, but can be used for tracking any list really, not just development work. See https://www.atlassian.com/software/jira for more.
-
This is a classic mistake by new administrators. Never put the resolution on any screen other than a "transition" screen. To fix this problem now, go to the project affected's configuration, find the issue type screen scheme and descend into it. You should see it maps different issue types on to different screen schemes…
-
This is a classic mistake by new administrators. Never put the resolution on any screen other than a "transition" screen. To fix this problem now, go to the project affected's configuration, find the issue type screen scheme and descend into it. You should see it maps different issue types on to different screen schemes…
-
Yes, they will work together.
-
Yes, feel free to ask more questions!
-
If you have no validator on the create transition, and the resolution is not allowing it to be set mandatory (some versions of Jira did it, but not yours, so we can forget that), then you must have an add-on providing some validation that we can't see. As the field config can't be the culprit, I would want to check the…
-
No problem, it's not something that's particularly obvious!
-
I don't, I don't use Cloud much any more. I thought it was under your profile settings
-
So nothing to do with printing, more about seeing standard output. Have a look at the printing/pdf output options. You can define headers in there for output.
-
Ah, ok, that's a bug in the "new issue view" (one amongst many). You can turn that off in your profile, and you should find you'll be able to enter time properly again.