Comments
-
You are not the first person to report this today, I think the latest Cloud update has broken something. This needs to go to Atlassian as a new bug in my opinion.
-
It did not always do it, but one of the upgrades removed the check for some unknown reason. My guess would be some people who want to make life hell for their users were bypassing the check to make apparent duplicates like "Fred", " Fred", "Fred " and " Fred ", so Atlassian dropped it. I still argue that allowing it is a…
-
This suggests there are a number of hidden issues - the board should be showing 24 issues, not just 4. I suspect the 4 on the board are not the 4 that are going to be carried over. Could you do a search for "sprint = <name of sprint>" in the issue navigator and see what issues that returns, and check their status and…
-
My best guess is that you do not have the global permission for "create shared objects" - check with your admins who does.
-
But who has the project permission for modify reporter? Can you check the permission shown for that project as @Elifcan Cakmak has shown?
-
What sql file? What exactly have you lost and what are you trying to get back?
-
I am sorry, that does not explain it. But I will take a guess. When you attach a file to a page, you're in the page already, there's no need for a location selection process. If you want to attach a file to another page, you select that by going to the page to attach the file to.
-
6.1 -> 6.4 -> 7.0 -> 7.6 (although I'd recommend 7.13 - the more recent the Jira version, the easier the migration to Cloud) Do NOT skip 6.4 to 7.0 - it causes all sorts of problems later in the process.
-
There is no "jira project" and the phrase is too vague to work out if you might mean "Jira Software" or "Portfolio for Jira", but as you don't mention planning or scale, I am gong to assume you mean Software. I think you are going to need two sets of licences. * Agent licences for Jira Service Desk - 5 of these for your…
-
Same here, it's not going to be there for much longer. And there was a security problem with it recently.
-
No, Confluence is not a spreadsheet, tables are very simple and don't do calculations.
-
What location option? Please explain that?
-
There is no "field level security" in Jira. You can control editing to an extent, by making "edit field X" a workflow action instead of an edit (and adding conditions to the transitions you add for it), but you can't hide a field at all. On server, the Quisapps field security app is the best solution, although Scriptrunner…
-
You've contradicted yourself here, so I am now confused. At first, the query was slow at 4 minutes, now it's fine at 102ms. Which is it? Is there still a problem?
-
Nothing changed that I can see in our Cloud systems. I suspect one of your admins may have changed permissions somewhere.
-
Some users in cwd_user will have login ids, others uids, and you're going to need to do multiple conditional joins to work out who is who. Please, stop reading the database, it's complex and not designed for reporting, as you've discovered. Please use the UI and REST API as intended - these will both give you consistent…
-
Could you expand on what you expect from the "swap api", specifically what you expect it to do differently to the documentation?
-
Ah, right, yes, that's a browser add-on or tweak. In Chrome, you can do things like adding https://jira base url/secure/QuickSearch.jspa?searchString=%s with a key of "tracker" or whatever you call your Jira system (I have access to a lot, so I don't just use "Jira"), then Tracker BUG-1234 should go straight there. For…
-
Still should work - format is <Jira base url>/browse/BUG-123
-
People don't tend to care about the "watched" filter alone. It's usually more like "I know I watched something <with several other pieces of information>". The list of things you're watching is not like the list of things you need to get done.
-
You might want to ask an admin about "bulk edit" permission. If they grant it to you, it will appear in the tools menu for the navigator. Watching and "open issues" are totally different things. An "open issue" usually means "assigned to me, so I am the current person responsible for it, and it is not flagged as…
-
"Jira is slow" - your admins need tools to help them debug why people are thinking it is slow. After the obvious ones like checking the network and client machines are ok, then you move on to want to knowing what Jira is doing, and that means logging and profiling. Or bugs, or faults, or flaws, or if an add-on does…
-
Yay, another blurring of descriptions of something that used to make sense from Atlassian! There are some fields you cannot move between primary and secondary (mostly primary fields often called "system" fields - ones that are part of Jira off-the-shelf and too important to be dropped to secondary).
-
Oh no, not in the slightest rude! Understandably frustrated and annoyed about where you have ended up, but not rude at all. The most simple option is Advanced search (not the "smart search" in the bar, but Issues -> Search, or do a smart search and you'll land on the main search and can click "advanced") and enter the…
-
What do you mean by "primary" and "secondary"?
-
Yes, but it will respect permissions - the account doing the reporting needs to be able to see the Jira issues.
-
The admin section is there to enable you to change the levels of logging and profiling. The main reasons for wanting to do that are debugging problems.
-
Best solution I've seen is still @Guillermo _DEISER_ 's Profields app, although there are now tricks you can play in some other apps that can help. Atlassian have still got a native implementation buried very very low in the backlog.
-
The include and include-excerpt macros are the first thing to try out to see if they can help.
-
The free ones I've seen have little interface points and no support, so I can't recommend them. On paid, I would use scriptrunner for the reasons I mentioned already, but you might want to check out powerscripts, automation and autoblocks as the main ones that might help you most flexibly.