Comments
-
This is usually caused by having a database that does not accept the higher range of emoticons. With Atlassian tools, we see this a lot with MySQL based installations, as the default collation does not support the upper emoticons. What database are you using and what are the collation settings for it?
-
There is no "patch", you have to do a full upgrade. As I don't know what you have done here with a "patch", I can't start to work out what you might be seeing.
-
Only by amending the core code in Jira (which will leave you unsupported and make upgrades a lot harder) These buttons do one thing, and they do it well. Could you explain why you want to change what they do? We might be able to give you alternatives to "hack the core code" if we know what you are trying to achieve.
-
The main question here is "How can global business put more pressure of global political leaders to finally, effectively address this global challenge?" This is the wrong question. Most global businesses are diametrically opposed to doing anything about climate change, because the money is in doing things that cause it.…
-
Ok, that sounds like the session data in the browser is getting confused. I'll try to be simple and just use tab examples, but it could be more complex. Imagine Tab 1 is opened and goes to the epic, then you open tab 2 and open and update a story. It is possible (although most sane browsers would not do this) that posting…
-
Jira does not track the usage of people writing to it in this way, and it does not record read activity at all. You will need to find an app that adds such logging to your Cloud instance and then use that to do the reporting you want.
-
So, I'd love to answer this one, but I'm not certain enough of what I'd like to say to do it. My instincts are * Not a direct bug, but a feature of how Jira's plugin system interacts with SR and Velocity, which is clumsy in places. Maybe a bug that happens because none of the three elements thought about that one…
-
These are not things most of us see in Jira, as most of us don't look at random bits of code out of context. Could you explain where you are seeing this, what the actual fields look like and why you are looking at the code?
-
When you apply the new scheme to the project, Jira will ask you how you want to migrate each of the old status to new, so your existing issues will take on the new status in the right place.
-
* Remove the field from the edit screen. * Create new screen that has the field you want to protect. * Edit the workflow, adding transitions to each status. These transitions should * Have the screen with the field on it * Go back to the same status * Have conditions that only allow people you want to edit the field to use…
-
The cat. One of them would love it - she likes cheese...
-
How are you defining "completed"?
-
Not that I can find. I think it's because you could have way more fields than you have keys on a keyboard, albeit doing that is bad for your people and you should really be building screens where they don't need shortcuts.
-
No (significant) updates on the request linked to above. It's pretty much "one type is epic, go get Portfolio or Align if you want more layers"
-
Cloud does not support the methods used to do the formatting, it can only be done with a "type 2 plugin", which you can't install on Cloud. Atlassian have a small handful of type-2s on Cloud but are committed to getting rid of them, not adopting more. If Cloud eventually enables us to do formatting with a Connect plugin,…
-
Start at https://confluence.atlassian.com/adminjiraserver076/upgrading-jira-applications-945110880.html 7.6.0 to 7.6.15 is a trivial upgrade, you should not have any problems with it and I would expect the upgrade process to be really fast, as there's little or nothing to do in the database!
-
How do you know they are "resolved"? What are you looking at? I ask because my guess is that you do not have the same idea of what "resolved" is as Jira, so while we may think an issue is resolved, we're not looking at what Jira is.
-
This is not something Jira does natively - issues are all separate entities and an update on one has no effect on others (ok, some calculated stuff, yes, but no field overwriting field on other issues) You must have some automation or script added to your system that is doing this. You'll need to find and fix that.
-
There's no way to "force" a human do something in a workflow. You can stop them doing things they should not, but the day anyone tries to force me to do something is the day I tell them to <insert your own bad things here> You should create an environment that encourages people to do it the right way. Don't say "you must",…
-
I do prefer "defect" myself - non-developers clearly understand "bug" is "something wrong in the software" and I like to use "bug" for "someone reported a bug", keeping "defect" for a subtask telling me "it failed a test or is not behaving the way the developers said it was going to"
-
Not a "workaround", but the way Scrum works. You do not estimate sub-tasks because they are irrelevant to velocity, deliverables and hence burn charts or prioritisation. This is one of the things people new to Agile don't often understand at first, it can take a while to sink in that your estimates only matter at a story…
-
"Postman" usually refers to a program that is used to investigate or manually talk to a REST API in a gui (rather than in a command line or background program) There is not really any "integration" to do between Postman and Jira. Jira has a REST API, Postman is a tool for using REST APIs. Fire up Postman, connect to Jira…
-
Directly in the UI, no, I'm afraid it is not. The quickest option I've found is to open the page in edit mode, select all the content, then paste it into a newly created empty template. Clunky, and sometimes some elements need a bit of tidying, but it mostly works.
-
Atlassian writes Jira, and also provides hosted systems on it, but they do not administrate other people's Jira systems (beyond what is required for hosting Atlassian Cloud, or when there's a support case that needs admin to investigate/fix) You will need to talk to the administrators of your system. There is a chance that…
-
Sorry, this is likely to be a much longer answer than you'd like. If it's a "classic" project, you'll need a Jira admin to add "bug" to the project's "issue type scheme" If it's a "next-gen" project, then the project admins (or Jira admins) will have to enable bugs for the project However, bug might already be there. It…
-
No change, sorry. It's because moving issues is not something you should really do a lot, and when you are doing it for the right reasons, you usually don't want to change the status. Because of that, Atlassian have tried to keep it as simple and plain as possible. The the use-cases for it are "user error when they picked…
-
No problem. This is one of those quirks in software (well, life in general really) - you might well have seen it mentioned in many places, but until it bites you for the first time, you won't really get it. Every Jira admin has been bitten by it at some point! Hence "inexperienced"
-
I think you'll need to talk to the administrators of your Confluence system - we're a community of Atlassian ecosystem people, most of whom (if not all) have no access to your Confluence at all, let alone any admin rights over it.
-
My best guess is that an inexperienced administrator has put the "resolution" field on the issue edit screen. You need to get that removed.
-
There are no docs for any recent "greenhopper" versions because there is no "greenhopper". The name is a hangover from years ago that still has not been refactored out. When Atlassian acquired it, they rebranded it "Agile", and then when Jira 7.0 re-architected from a plugin to an application, they rebranded it again as…