Comments
-
Still doesn't matter, that could change any second, and also is not updated on some changes because it's irrelevant. When working with Cloud, the answer to "what version is it?" is just "Cloud"
-
The CSV import creates issues from a list. To "get" them, you, well, just use Jira. Look at the issues you've imported.
-
No. Have a think about the word "anonymous". You can not identify a truly anonymous person/process/computer/etc, that is what anonymous means. Your setup is literally "I do not know who you are, so you can see any space with the 'I do not know who you are' flag set". This is not a difficult concept at all. If you want…
-
No. Upgrade to 5.9 to fix this (or at least 5.4.8)
-
No, you've misunderstood what Vimeo is doing. First, each video translates to a space in its own right, but secondly and more to the point, the access is done with a shared "secret" (that can be worked out). It's not anonymous access, the link is the identifying login for a user.
-
An anonymous user can only see the spaces that allows anonymous access. You can't hide an anonymously accessible space from an anonymous user, that's a flat out contradiction. They're anonymous and you've told Confluence that anonymous users can see the space.
-
It's entirely possible that Cloud has been changed to use numerics instead of login recently.
-
I'm afraid not, Jira sticks to "the single right-most column is done". You can put more than one status in there though, so both your "done" type status will fit.
-
Jira 7.9 has some of it, 7.10 a bit more.
-
The project summary contains a description.
-
There's a reasonably reliable way to work it out. If the version is not on any issues, he did it from project -> versions. If it's on one issue, it's almost certain that he did it by editing that issue. If it's on lots of issues, it's the "release" on the Kanban board. (I'm not 100% sure on the second and third because it…
-
There's not a huge number of Golang experts here, so you might want to expand on this for a wider audience. Could you show us the body of the request that your code builds and posts to Jira?
-
I'll vouch for it. There might be other reasons, but you definitely get the unique numerical id for a user when a user name contains non-standard characters your setup cannot handle.
-
Never hide things that show user uniqueness. I hold up a case where one system had 9 people with similar names and constant complaints about the wrong ones being chosen. I'm glad you can't do this in Jira, it's a bad bad idea.
-
Odd, I get a "add new" when I do it. You are a system admin?
-
Hmm, that's worrying, it implies your javascript is doing REALLY bad things! The other option is to go to the default field configuration, and repeat the exercise with replacing the ID in the "edit field X" link. Field configurations go a different route and hopefully won't run into that 500 error. If that does not work…
-
You're already part way down the best path to configuring SSL. I always recommend you get Jira up and running (and briefly tested) over http before starting on SSL. Once it's running ok, stop it and run through https://confluence.atlassian.com/adminjiraserver071/running-jira-applications-over-ssl-or-https-802593051.html As…
-
There's another hack that requires no clever code. Create a "scraps" project. I usually giv it a name people will never want to use for real projects, and a permission scheme that is "administrator only" Create a spreadsheet with two columns. One column contains the options, the other column should contain something unique…
-
We need to be careful here. Do you genuinely mean a "checklist" field (as provided by an add-on), or is that you describing a standard "checkbox" field? If it is a check-list, you have to use a validator on it, you can't make it mandatory in field config. But checkboxes do work, the will force the selection of one or more…
-
An issue collector is a bit of javascript that a project can generate for you and you drop into your application (in a Confluence space, use the custom html option to do it). It will place a box on your screen that expands out to a "create issue" type box for the user to fill in.
-
People with the right to create versions can also create them when simply editing or creating an issue. People with board admin rights on a Kanban board can also belt "release" to create a new one.
-
How are you telling Jira that there is an incident against the issue? Comments? Sub tasks? Linked issues?
-
Yes, sub-tasks belong to, and are part of a parent issue. I think you have dependencies here, not sub-tasks. I'd be looking at Portfolio and Big Picture for cross-project planning and allocation.
-
Only Kanban boards have the "release" function (or agility if you enable it for them). Core boards simply drop "done" issues when they've been there for a fortnight.
-
Use the permission scheme to say "Edit: Reporter, Assignee" and no-one else. You'll need to think about how you allow B to assign it to themselves though.
-
It sounds like what you are calling "sub-tasks" are not sub-tasks, but issues in other projects.
-
Because Atlassian have decided to redesign their software, and you signed up to have the latest stuff when you chose Cloud. I'm not a fan of it either - far too many Cloud users are asking me questions about basic navigation that were never asked before because they could find their way around. I've tried it out on my…
-
The first log is telling you that someone or something told it to shut down at 2:03. Have a look at the application log for that time. The second log is not a crash report, it's telling you that there's something wrong with your https setup. If you're not using it now, you can ignore it (although I'd still recommend fixing…
-
You're stuck with it. Unless you move to Server.