Comments
-
It's a long way away. When I asked, the only thing I could get was "very unlikely before the next US summit"
-
Yes, that's correct, labels apply to pages, not bits of text. You can comment on text from the page view, but labels are for pages.
-
A 404 on this call means your user is not logging in, the issue given does not exist or your user does not have permission to see and/or transition the issue.
-
When Jira puts that error on screen, it will also write a similar message to the log, with more detail. Could you check the application log for it? jira-home/logs/atlassian-jira.log
-
Yes, check the permission scheme, and amend it so that you can put people in a role that has no "create", but does have "edit"
-
It's probably because large numbers of people make the mistake of thinking that boards belong to projects. Instead of making it clearer that they do not, Atlassian seem to have decided to make it look more like they do.
-
You'll need to fix your network so you can transfer a file of that size.
-
Again, this is nonsense. A sub-task is part of a parent issue and hence should be seen by the same people who can see the main task. Imagine you are putting together a Lego toy. Does it make sense for some of the pieces you need to be hidden from you? No.
-
See Ivan's answer. If there was, he'd have said.
-
There are two default filters on that menu that are useful for everyone (in testing, Atlassian found that if they were not there, everyone created their own which were identical). They are built in and cannot be removed.
-
The labels "field" appears when you click on the labels tag icon at the top of the page next to the name. Could you show us what you see there?
-
>The only workaround i could think of is allowing any logged in user "create issues" permission within our project....but that opens up concerns of users accidentally creating issues in the wrong projects. Eh? No it doesn't. If you only give them "create" permission in the "Jira Support" project, then they won't be able to…
-
You are misunderstanding something. Off-the-shelf, Atlassian Cloud systems are set up to use Atlassian accounts for users. These are things that exist outside Atlassian Cloud, independently. They do not belong to you, they belong to the person. It is nonsense (and, if I read the GDPR notes correctly, soon to be illegal…
-
You should be careful with language here - it is flagged with estimate in the screens, but it is still named "Story points", and the scrum boards are the only place it does the flagging. Keep it simple and call the field by the name that is used everywhere, not the flag.
-
Could you explain what " flush the assignee " means?
-
Assignee is a very important field in Jira. It is always there. It names someone, or states "unassigned" Could you tell us where you expect it to appear?
-
For Issue template, I always think "someone wants to pre-fill an issue", not a set of them. The plural "issues" in there does make sense, but I had to read it several times before I saw it. I think your "Issue List Template" is far better, but also sort of want to say "Template a set of issues" The same opinion goes for…
-
Labels are intended to be completely free format for the users to tag things in any way they want. So, no, there's no reduction in freedom for your users. My personal feeling is that there should be one set of labels, but there should be two types - "official" and "free format". Give your users a list of pre-approved…
-
Forget about the "estimation" stuff, it does not matter. This simplifies what you are doing. You have Story Points in your import data. I imagine this is a number for each issue? When you do an import, you need to import numbers into numeric fields. So you need a numeric field to import this into. An "estimate" field is…
-
Very true, that could really hurt their capacity. I suspect it may have added quite a lot of lead-time to any planned increase in numbers!
-
Yes, they are still limited. There was a talk at the last summit about aiming for 5,000 for the next Summit, but I don't know how far Atlassian have got with that (it's definitely not there yet)
-
No, the confluence front end does not have any "network connectivity test" like that. I don't know where you're getting that from. Could you explain what you are actually doing and what you see on screen?
-
I'd challenge this a little. - It's not SSL that is unsupported, it's non-standard configurations. And they're unsupported because Atlassian can't possibly know what you're doing with your servers. So, authentications, load balancing, config tweaks, memory settings, and and and. In fact, I would recommend NOT using SSL at…
-
Do not touch an Atlassian system's database while it is running. Especially not with a root account.
-
JQL is not the same as SQL. It does not return data or say anything about how to present it. It simply gives back a list of issues that match. It is up to the presentation code running the search to decide how to display it. The issue navigator does not support grouping. Some reports do, but they do it in themselves, they…
-
Can't find anything in the marketplace. Could you tell us what this has to do with Jira?
-
True, although you can still get a copy of it from that!
-
The other site should validate whatever changes are needed fit with Confluence content, then update the page via a REST call.
-
You can't change it, you have to buy a new Cloud system and drop the server (if you've put data in, you can export it and load it into Cloud, and if you are in the first 30 days of your licence, you can get a refund on the licence because you made an honest mistake) I am not sure I understand "how do I get my own account…
-
Absolutely. Projects, config change, add-on requests, user access control and general help/support all tend to have different field and process models. Hence different screens and workflows, so you need different issue types. Obviously, when naming them, you should take the standard advice of not allowing too much…