Comments
-
You would need to rewrite the whole of Jira and all the add-ons to do this. The whole thing is designed for users to readily find issues within projects, and destroying that would mean having to re-write all the places that work on the <project>-<sequence> assumption. You could write something to fill in a field at…
-
Natively, it's a bit of a faff, but you can do quite a lot with user macros. However, I'd also look at the add-ons Content Formatting (for footnotes) and the Cite add-on.
-
No change - if you change the names of priorities, you can still break filters, which in turn will break boards. You'll need broken filters to be fixed by their owners.
-
It starts when you click re-index.
-
You probably need to explain "scored" in a less vague way, but without better information, my instinct lead me to look for this: https://marketplace.atlassian.com/search?product=confluence&query=gamify
-
You will need an add-on to provide a function for that. There is Script Runner for Cloud that can do it, but, as ever, you should evaluate all options.
-
Start at https://confluence.atlassian.com/bitbucketserver/migrating-bitbucket-server-to-another-server-776640406.html
-
Data Centre is for large user bases with multiple nodes and high resilience. It's a lot more expensive and complex than Server. Most of us need Server (if you install server and then decide to go to Data Centre, that's a lot easier than starting with Server and moving down later)
-
You'll need to contact your Jira administrators. We're a community of end-users here, like yourself. We've got less access to your system than you do.
-
Coding is the only way to do this. You'll need to write a new version of the pie chart (I say "write", I mean "take the existing code and tweak it to meet your needs")
-
No, you need Portfolio (or other add-ons) if you want more layers.
-
Validators run when a user clicks either the transition button (assuming no screen is there) or the "complete transition" button on a transition screen. They run in the order you add them to the workflow transition. Oddly, it does still run all of them, even if the first one fails, but it's easiest to think of it running…
-
People from both companies are going to need their own accounts on your Confluence. Both sets of people are users.
-
Labels are text strings, you can put user names into them, but they're not users, they remain simple strings (that happen to match users)
-
There are no add-ons that do this. You need to add the transitions. There are then add-ons which can give you conditions of "only allow this transition if it goes back to the last status"
-
Use one of the scripting add-ons that provides scripted or calculated fields.
-
If there's no "stuck" on the global list, then yes, either it's been removed from the list or deleted. You're right in that it was definitely there, as the history shows it being removed from a workflow. I'm afraid the only explanation is that one of your admins renamed or removed it.
-
No, there's no direct relationship. But there's nothing to stop you holding your developers to a 1:1 rule, and the system does tend nudge people toward "sprint X delivers version Y"
-
The windows evaluation servers will work - they're still a full install of Confluence, they've just not had any optimisation done for production use (not that the other versions have either)
-
Remaining estimate is stored, but also calculated which makes it "fun". In a simple case, the users put in an estimate of X, then several worklogs are added, recording time as (say) y1, y2, and y3, giving a total of Y, then when you look at the issue, the "remaining estimate" is simply "X - Y". But then it gets complex.…
-
Yes, absolutely, that's also a very good way to do it.
-
Ah, Atlassian applications generally do not like older versions of Java. You need to go via "bridge" versions usually, ones that supports the old version of Java and the later one.
-
It generally means the server on the other end is not responding. Hard to tell if it's a proxy or raw service from just "504", but the answer is the same either way - you need your server admins to check that it's all running ok!
-
One of them, the assignee, is the owner. If they want other users to be involved, comment, have a field for collaborators, or have a group field to share. But an issue should always have one single person responsible.
-
Took me a long time to notice it, and longer to try importing it on a whim, just to see what it was! Nice trick for "reset" though.
-
>I tried typing Town Team in the Assignee one, but it says "No matches". Ah, that explains it, you have misunderstood the point. The assignee is the user responsible for the issue. You can not put a group in there, because it's a terrible idea that opens you up to masses of lost or neglected issues. The doc you have found…
-
No, projects are the containers for issues, an issue can only exist in one project.
-
Yes, the system information page has, unfortunately, been removed from view.
-
Yes, correct. When you enter localhost, it's your machine. When your users enter localhost, it refers them to their machine, where your Jira is NOT running. Get them to use the ip address of your machine. But, a much better idea is a dedicated server, with it's own name and hardware, so they're not dependent on you being…
-
Only what Mirek stated - "Rule is simple: If you have access to the page you will have access to the attachments". That's working fine for me.