Comments
-
It's not quite "included", it's better to think of Service Desk and Software as applications that sit on top of Core adding functions to it. The installers for those two install Core first and then add Service Desk or Software in top without the user having to think about it.
-
We need to see what the server is doing at the time you try this action. Without the surrounding logs (from the time you click to the time you get the error message), all we can really tell you is that there's something wrong.
-
There is no "split" in Jira, but it's not hard. Use "clone" and then amend the cloned issue to suit.
-
That sounds like you're not importing a resolution from your external system. What exactly are you putting in the CSV?
-
Option 1 is still the right thing to do. You have "fielditis" and that's going to cause you other problems in the long run. There is no "fix" for this, and as far as I can see, Atlassian have no plans to do anything about it.
-
No. You cannot install Type 2 plugins on Cloud. Cloud only supports Connect apps.
-
There should be a lot more than that.
-
There's no need for the reporter to vote - the implicit assumption is that because they raised it, it counts as a vote.
-
Atlassian don't do telephone support (unless you're a premium customer), so that is not going to get you anything. You need to ask Nahum to answer Ann's questions about how the issue was raised and where.
-
Issue type changes are recorded in the history, so yes, you can write a scripted field that would go back through the history and find and expose issue type changes.
-
I've done it with Jira, over REST, so I know some stuff can be done with Cloud. What are you looking for when you say "connect"? Bitbucket is for git though, not Subversion, so I'm not quite sure what you're aiming for.
-
You'll need to read the logs to see what the error is. Start with the application log named in system info (generally should be <jira home>/logs/atlassian-jira.log )
-
It's not saying anything about moving, it's saying there is a page in the target space already called "Project List". Try renaming the source page before moving again.
-
That won't work. You need to attach the issues via the API, which means going through the UI, REST or email. The structure of issues is in no way related to the Windows Explorer view.The best you can do is have some file store somewhere that is monitored by a process that can scan it for new files, work out where files…
-
No, you have to go through the support request you've raised.
-
Looks simple to me - issue-123 is not "done", so it doesn't count towards the burndown yet.
-
No. It means just 15:00.
-
A quick test - could you turn off collaborative editing (in the admin menu) and try editing again? If you can now edit (with the old style editor), then there's something wrong with your Synchrony setup. If you still cannot edit, then we'll need to start looking at the logs.
-
It's not a bug, it's by design. The user, by making themselves not the assignee, is removing their own right to make comments. The comment and assign actions are happening at the same time, and going to a state where the comment can't be made.
-
No. You should never write to a Jira database. If you do, it should be infrequent and always done when Jira is offline and you've taken a proven backup first. I don't know who "sold" it to you on the ability to get to the database, but they were wrong and it's been mis-sold to you. In most cases, you shouldn't even be…
-
You could write a user macro to list all the spaces with their attachments. Although it could be very long, and your "space address" column is not of much use because they all live in Confluence. Space Key might be more useful.
-
You will need to write a listener that can catch user events and create the issue as required.
-
It's not clear what is blocking you from accessing your Jira. If it's behind a corporate firewall, then a VPN, as described by Tayyab is a very good option. But there may be other reasons. Have you exposed it to the internet? Have you firewalled it off and are thinking about whitelisting a handful of ip addresses access…
-
Not without hacking the core of Jira apart.
-
No. Jira Core is the Jira framework. Jira Software and Jira Service Desk are applications that add functions on top of that framework. You can get Jira Service Desk and Jira Software as installer packages, but they are just bundles of Core + their application. Confluence is a totally separate system with its own install.…
-
You need code to do that. Something to read your data and display it as a field. There are "database fields" add-ons in the marketplace which allow you to draw their options from a database and to display SQL queries too, it's worth a look at those, rather than writing your own. A better option may be to use something like…
-
What does the log say about it? If Jira is reading an email from a mailbox and is unable to process it for some reason, that will be recorded in the logs. Have a look at the files in <jira home>/logs
-
I agree with this - unless you are absolutely certain you need separate Jira instances, take a good look at getting one single one. "Please merge my Jira systems" currently gets Solution Partners quite a lot of work...
-
You will need to have a transition from the new status back to the old one. This will not stop the users just commenting and not changing the status, but you need the transition before you can do anything to fix the problem. You could force the users to use the transition by blocking comments on the "pending" status.…
-
Depends on what you mean by "observer", but I'd guess you want "watchers". In the "people" area of an issue, there is a "watchers" list - clicking on that will take you to a screen where you can add people to that list (or remove them from it) You will need to make sure you have "manage watchers" permission in the project.