Comments
-
A board is a view of a selection of issues, not a segregated container. You need to change your board filters so that they only select the issues you want to see on them.
-
See https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html But, broadly, the process is: * Upgrade your Server to the very latest available versions of the applications you have (Core needs to be 7.8.0 at the time I'm writing this) * Check what add-ons you are going to have to lose…
-
As above, Confluence does not do this natively, you'll need to look at add-ons such as Sub Space and Advanced notifications
-
A board is not a container for issues, it is a view of a selection of issues. Your two boards are running filters that both select the new issue, so yes, it's going to appear on both boards. If you want different sets of issues on the different boards, then alter their filters so that they do not select the same issues.…
-
I'm afraid Jessica's post is out of date. You need to do this disable/enable thing in the properties file only.
-
Yes, quite a lot of people allow anonymous access (not logged in) to their systems. Also, users with little or no access because they've been removed from all groups and roles etc, but not actively disabled or deleted will still get access to anything using "all logged in users", which is a widely used default. (Although…
-
That suggests the fields are not available in the project you are trying to import into. Can you try creating an issue in that project and see if you see "original estimate" and "story points" in the create screen? (Don't worry about remaining estimate at this point, it's kind of a composite field with original estimate -…
-
You will need to write javascript that sets a cookie on the user's machine to say "this person has clicked close already" and then checks that before displaying the banner again. I'd strongly recommend not bothering, it's a lot of effort for little reward. Instead, try making your banner message less annoying and intrusive…
-
What does the "Configure board -> Columns" tell you the mappings are?
-
Ok, you'll need to look at the conditions on the workflow directly. The permission helper cannot tell you about those in full, especially if someone has put in conditions that are not the native Jira ones.
-
Have you followed up on the previous two answers you got? Can you tell us why they have not fixed it?
-
Yes, SR can do this. A scripted condition could easily check the issue history for "last person to execute a transition" and return "false" (meaning "no, do not allow this user to use this transition") if that user == currentuser()
-
Indeed, it can't be done. If a user can assign an issue, they can assign it to anyone caught by the "assignable user" permission. It's not limited by who the assigning person might be.
-
That's part of the SQL you need to run to get the answer you are looking for.
-
See https://confluence.atlassian.com/jirakb/jira-how-to-migrate-from-hsql-database-to-an-external-database-295308246.html
-
Comala are usually good at turning out new releases, I'm sure you won't need to wait long.
-
If you are on Server, then you should find Comala will release a new version soon to match the latest Confluence that you are on. If you are on Cloud, then you will need to move to Server in order to be able to install it.
-
There is no "table" custom field in Jira. You will need to use one of the add-ons that can provide it - see https://marketplace.atlassian.com/search?product=jira&query=table for them
-
No, and there is no column "date" in your output, there's created and updated. Could you try the query Matt gave instead, so we can see the actual table? It also looks to me like whatever you are doing this SQL with is dropping the time from the "created" display as well. From memory, there's a couple of MS-SQL tools that…
-
No. The only way to change the status of an issue is to move it through a workflow transition that takes it to the new status.
-
I was just about to post much the same. Changegroup in Jira 6.4, 7.1, 7.2, and 7.8 looks exactly like that, with a "created" date/time stamp, not "Date" without a time.
-
Sometimes. A version of Service Desk may work with a range of versions of Jira Core. Check under "manage applications" and you'll see if you can upgrade there.
-
No. If someone can see a project, they can see all the project data.
-
It happens automatically when the certificate is asked for, the JVM handles it.
-
They are not related. A project is a container for issues. A dashboard is a place to place sets of reports (most of which will be drawing information from projects, but there's no direct relationship)
-
Changeitem stores the line (status changed to status, on one row, with any other changes made in the transition in their own rows). Changegroup stores the date and time of the change.
-
Jira hides (most) fields that have no data to reduce clutter. It's always done that. It's annoying for those of us who use inline edit in the view screen - I don't think they thought through inline editing too well when it was introduced in 4.something, and the problem with empty fields persists. If it had been me…
-
Yes, as mentioned above.
-
An upgrade won't touch the field configuration scheme like that, might be worth a look in the audit log to see who changed it. To fix it though, get the admin to start at the project level. Go into settings and look for "fields". This will give you the list of field configurations in use in this project (there may be only…
-
One of your admins has changed the field configuration scheme such that due date is mandatory. You're right in that due date is not needed for your process, so I would ask your admin to undo their mistake, rather than get due-date added to your screens.