Comments
-
No, the conversion process just changes the issue type. You'll need to link the issues manually (or with a scripting add-on)
-
Jira already has a voting system built in. (I think it's far too simple, but it's worth a look before you go for add-ons) Discussion documents are usually done in Confluence rather than Jira, as it's built for that, whereas Jira is built to be an issue tracker.
-
Does this user have the space permissions required to use this space?
-
Could you give us the full unambiguous error message? You say "getting unknown user macro error", but this is not clear because you might mean the error is unknown user, or "unknown user macro" which Confluence should not throw (a page doesn't know if a macro is a user macro or one from an add-on) Whatever the error…
-
Do not update the Jira database. You are almost certainly going to get it wrong, and break it. If you absolutely must do it with SQL, then you must stop Jira, back up the database, prove you can restore a Jira system from the backup you have taken, then run your SQL, restart it and re-index before letting the users in. If…
-
Do you have issues in the "done" column? If you do, are any of them sub-tasks?
-
Do you have "resolve issue" permission? This would stop you being able to put a fix version on issues, which blocks the "release" if you cannot do it.
-
Have a look at your network, and make sure it can reach and read data from https://common-admin-cdn.atlassian.com/
-
Confluence on Cloud runs on https://<your chosen name>.atlassian.net which is SSL already, and has nothing to do with your site address. I think you need to explain the question more.
-
It's been "done = right hand column" since Jira Agile created the Scrum boards and dropped rapid boards, so I assume your fix is to get the status into the right column.
-
Cloud accounts are of three types. They are managed by * The user having a Google account where changes to email address are done in Google, not Atlassian Cloud. * The user having an LDAP/SAML ID provided by your organisation, where changes of email address are down to the admins of the organisation's directory * The user…
-
Yes, the original issue key as created. Jira retains the information that you moved it and takes people landing there to the new issue. If, for example, you create ABC-123, the url is <jira base>/browse/ABC-123 . You move it to project DEF and it gets numbered 456. <jira base>/browse/DEF-456 is the new direct url for it,…
-
Start at https://confluence.atlassian.com/doc/upgrading-confluence-4578.html - there is no "migrate", you just upgrade.
-
There isn't one.
-
It's <base url>/browse/Issuekey - the issue ID is not really for humans and isn't exposed in the urls.
-
Set the board filter to exclude them. If, for example, your board filter currently says "project = X", then use "project = X and issuetype in standardTssueTypes() and issuetype != task"
-
What is your question? If it is "what is wrong with my validator / Department of Defence?", then you need to give us an actual explanation of "it does not work". For all we know from your statement, it could not be working because there's an angry penguin stopping you from using the computer
-
No good until they go up to 11 (Please some one stop me from watching documentaries)
-
WE don't really know, because it was not followed up with an answer 5 years ago. The code for user access was pretty much re-written when Jira 7 and Confluence 6 arrived, so even though you might see a similar problem, everything has changed since this was asked. I would recommend that you write up your problem as a new…
-
Start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
I think you need to explain this more. You've tagged it with Jira, but said "add page", which is a Confluence function, and you've not explained where you want to move from or to (as add page is already in the top bar, part of the menu)
-
Those warnings are probably related to the error, but we need to see the actual error the process throws and a description of the behaviour of the front-end with the exact errors you are seeing there.
-
Macros are part of the content of a page, not pages or anchors. I don't understand what you mean by "link page to macro". Use the macro on a page to hide things in expandable boxes.
-
Do not unlock fields - they're locked for a reason (stopping you from putting in broken config)
-
>Recently, we gave our customer access to browse the project with a "User Role" Ah, that's not the intention of Service Desk. You can do it, but it means your customers are no longer just customers, they are full Jira users. The intention of Service desk is that customers see only the requests that front the issues. There…
-
You'll have to use the old archived account, change the email address on that (from id.atlassian.com) and then you'll be able to create a new Atlassian account with the email address.
-
Thing is, there's no actual error here, so I'm not sure why you were messing with the settings. There is a warning, but the command executes fine.
-
I'm a bit stuck. Maybe a screenshot of the board and report might show us something?
-
What does the tooltip show when you hover the cursor over the red cross to the left?
-
Ok, the error messages you are getting do not appear to be Jira reading a user picker field, but a text field instead, and it's struggling with the default value for it. Has this field been somehow converted from another type?