Comments
-
You'll need to write code to do this "integration". The problem here is that "integrate" is mostly a suitcase word - gives us a rough idea, but we have no idea what's inside it and hence cannot tell you more than "write some code to integrate them"
-
Field descriptions and the announcement banner are the usual place for javascript injection.
-
I can't see what's wrong there, or why you are not pasting your licence in. But as you're stuck, and I can't see it, try https://support.atlassian.com/contact
-
Yes, it absolutely does sum them up. You can click on the button to toggle the parent's view between "this issue" and "this issue and sum of all sub-tasks" in the main issue view. However, that is only done in the issue display, and in the issue navigator when you use the "sigma" fields to display the sums. Jira Software…
-
You absolutely should not be using the embedded database, it is known to fail without warning and catastrophically when it goes. You could lose your entire system at any second. Confluence does not care if your database is clustered, it just needs something that appears to be a single reliable datasource in one place that…
-
Jira doesn't have "cross project versions", so I'm curious as to what you think you were doing there.
-
Yes, but it will cause Jira to think all your resolved issues are still open and unresolved. You should not hide it, just use it as intended. Clear it on "re-open" with the simple "set field to" post-function, and set it on "close" with either using a resolution screen, or setting it with the same "set field to"…
-
You only need the recovery admin password once, so that you can get system admin on Confluence. Once you have it, you should make people admins, with their accounts, so you don't need it any more. Then you should set up a backup strategy (recommendation - at the very least, back up the attachments and take a standard…
-
This suggests that issue 1 and 2 are of different types and/or project, and have different "edit" screens. Check the issue type screen scheme for issue 1 contains the field in the edit screen.
-
You'll need to report this to the vendor of the add-on, so I can't tell you unless you can identify the add-on. Could you list all the user-installed add-ons - we could help you rule some out or identify one that might be the cause.
-
I still need to see the screen shot, ideally from where you land on the dashboard - from the top of the browser down to the name of the dashboard.
-
Your screenshot is showing the whole bar. I don't understand what you think is missing from that?
-
An expired Jira licence will still have the bar at the top, just not with much in it. If that bar is missing, you will need to talk to your admins. Although, could you give us a screenshot? I've got one last thing it might be, but it's hard to explain and not worth it without being sure.
-
It is not a mandatory field in the standard Jira way. There is nothing you can do about its behaviour this way, you just have to use it properly. That is never put it on any screen other than view or transition screens on transitions that go into a "closed" type status. Do not put it on Create or Edit (in your case, you…
-
Ok, if the whole bar is missing, there are two possibilities A very heavily customised Server Jira where the customisation has either moved it elsewhere, or become broken. Without knowing what the customisation is, we can't help you. We'd need your Administrators to explain what they have done You are on Cloud Jira, where…
-
I'm sorry, but I still can't work out what you are expecting the field to do.
-
Ok, you've either hit a bug in Jira Software or you've got a broken add-on or javascript hack that is breaking the screen. As this is Cloud, I suspect the first to be a lot more likely, and I'd want to raise it with https://support.atlassian.com/contact
-
You can't hide summary in the field config anyway, it is a mandatory field. If it's not on a user's screen, get them to check the "configure fields" at the top right of the window. You'll find it hidden in there.
-
It's the same answer - if you are missing the create button, then you do not have "create issue" permissions.
-
No. Cloud is completely hosted - it's all or nothing (barring some add-ons which allow you to store attachments on google drive)
-
Yes, that's correct, your javascript is being run in the wrong place. It's being rendered too late in the page generation. You should not be injecting javascript like this, it's not going to work the way you want it too, it's unreliable and hard to maintain. Defaulting the summary suggests you're misusing the field as well…
-
Try a search engine for "release notes" for your version of Jira, I'm not going to google it for you. For the scripting suite, you have not said which one, so we could not google that. But have a look for it on marketplace.atlassian.com and look at the versions, almost all add-ons publish release notes there.
-
There's no need for a "quote", pricing is public: https://bitbucket.org/product/pricing?tab=host-in-the-cloud
-
They are issues in the project(s) your board includes that have a status you have put in that column. They will appear on the board if the board filter selects them.
-
Some will, some will not. You really should not be using javascript to do this, unless it's bundled into an add-on where you can make the calls dynamic so you don't need to worry (i.e. they work out the ids, not hard-code them)
-
Have you worked through the troubleshooting doc mentioned?
-
The best way to do it is put them in roles that allow them to see the issues.
-
The edit option lists all available fields for the issues, alphabetically. If you have added the resolution to the "edit" screen for the issues, then it will be in there.
-
Ah, I see. Can you try the plain issue view (not Kanban) and see what a transition screen there does?
-
Bulk edit offers you "edit" on the first step.