Comments
-
The issue collectors are a short block of Javascript that inject a standard box. You can wrap your own javascript into them to make it match with your site better.
-
Ok, that's a bug in your workplace, if it's not re-reading Jira on refresh.
-
It's a better model than imposing restrictions. And if you have 9900 users, I'd be suggesting you look at groups rather than individuals.
-
Thanks @bmcalary - I didn't know the Australian one had opened!
-
>How and where should I name these 10 users in order to give them restrictions? You don't. It's not about stopping people seeing stuff it's about allowing them to. Either do not give them permission to see the space, or put restrictions on pages that do not allow them to see them.
-
The issue does not match your board filter for some reason. What does your board filter say, and what does the issue look like?
-
Not yet. The Atlassian Cloud data centres are currently only in the USA and Republic of Ireland. There are more on the way, but it's going to be a while. To keep your data in Australia, your only option for the next couple of years is to install Atlassian Server products in a data centre yourself (or with a 3rd party who…
-
I think this project is a "Next Gen" project rather than a classic one where you can have mixed workflows. Can you check the project type?
-
A sprint is a time box for your team, not individual developers. For each sprint, estimate how much the team can do in that time, and pull in issues that add up to (close to) that amount.
-
Yes, tick the "minor change I don't want to notify people about" box at the bottom of the edit page.
-
You can translate Jira to change words, but don't. * A lot of your users have used Jira before, and will do again. Having to explain to these people that "we use different words for things in this system" is work you don't need to impose, and you'll find it continues to confuse people well after the fact. * Jira already…
-
I don't know how you managed to do that! Unless you installed an early-access system instead of a production one, you shouldn't get future versions. Part of me wants to fix it by fiddling with downloads and versions, but the engineer in me wants to know if it is actually breaking anything - if not, and the support…
-
Code. You'll need to identify every css file that formats the issues and change them to remove the strike out. However, the problem you describe here is not the strike-out, it's that an inexperienced admin has added "unresolved" as a resolution and hence broken your system. You need to: * Go through all your screens and…
-
What do you mean by "issuer" of a filter?
-
For input, you can't do a lot - you are allowing your users to attach files, and that's about it. You can limit the size of attachments, but that's not a huge amount to do with picture size. In the display-picture macros, you can frame images at a certain size though.
-
Oh, sorry, I didn't notice the number discrepancy. It will ignore attempts to upgrades that would downgrade it!
-
I'd like a wrapper for all my tools - it's very common to see a site with a bar or landing page that then takes you off to various tools, and it would make so much sense to have that have a login as well. It is something I'd like to do, but I've never had the time to even begin coding! I suspect the easiest option is…
-
It's because the focus for Confluence is unstructured pages, not structured data that's probably better held in other systems. But I'd like to see better table content like this too.
-
Go to your test system, click update, test to see if it has broken anything. If not, then click update in production.
-
No, you need to add code to do it.
-
Yes. I would write a "scripted field" to work it out from the data on the issue.
-
Yes, they can, if you work with organisations that use them.
-
The attachments table is what you need to read, but there's no url or path stored. There is data that will enable code to work out where the file is on the disk. I think we need to know why you are looking for a "url" when there isn't one.
-
You should be monitoring your user levels in order to meet your side of the contract you signed up for. Your administrators have been mailed about the number of users and the billing does go up automatically (unless you've asked for it not to, or you've gone over the highest possible number) You need to talk to your…
-
Do not use even try to versions that are incompatible within Jira. They are not supported for good reasons (often that just "it doesn't work") Confluence is not a Jira application, it is a separate application. Version 5 will work fine with Jira 7.x although you might find the Jira macros aren't as useful as the ones in…
-
>There are cases where a particular Feature could extend over more than a Sprint. In "proper" scrum, that means you are not breaking up your stories enough and you need to look at improving your grooming. Stories should fit within a sprint. In real life, people do have stories that are too large, and when that happens, a…
-
Because they don't want to spend time implementing one form of SSO that would be useless to all the other customers who are using others. Plus, they already have SSO in their products via another route, so there's no problem to solve.
-
See https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html and https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html
-
Get your application to use SSO, or create a login token for the Atlassian application it needs to get into.
-
Your google sheet is not handling single versions properly, it needs to remove the , The comma is there as a separator between (possible) multiple options being in the field, and your sheet needs to strip it from the last value in the field.