Comments
-
Not in the way you describe it. I think your look at "user macros" probably is the way to do it. I have done this before, for pages that are talking about groups of servers. Imagine I've got 5 JIRA servers to talk about and I want each reference to one of them in my text to be a link to the server information page. I wrote…
-
A number of us have pointed out that Atlassian have made some bad mistakes on this move, including ignoring people who should have been properly consulted on being "champions" or something. One of my complaints named you as someone I'd spotted being ignored.
-
Ugh, no, you don't want to do this. You can, by allowing the "group" called "anyone" the "issue create" permission in the permission scheme, but you will end up in a mess because you can't track them. And you certainly can't put such a system on the internet - it's only going to last a few hours before drowning in spam. If…
-
No, because boards don't "contain" issues. Projects are the issue containers. Boards are a selected view of issues. Which makes your questions hard to answer directly because the concepts are wrong. But also, easy to answer at the same time You need to create a new board that has a filter that selects the issues you want…
-
Atlassian are removing the html from displays because it's a vector for security attacks. They've not got around to the admin screens yet, as admins generally have to be trusted no matter what.
-
I'd tend towards a week, as people do things like have a couple of days off here and there. Over a weekend is long enough though. That's assuming I got any emails from the site at all though...
-
10Mb max file size by default, and your total Cloud storage is capped at 25Gb for smaller Cloud installs (100 for larger)
-
I'd use one of the database custom fields in the marketplace to do this. I don't know what you mean by "how display a field depends on user's choice"
-
Look in the cwd_ tables. cwd_user will tell you about the users and which directory they are in, and cwd_membership will give you the membership of their groups. I'm not 100% sure I would give you the right "join" for the question you are probably asking, but cwd_membership alone may well be able to answer it
-
What does atlassian-jira.log say ? I expect that will contain some errors telling you why it's not proceeding.
-
Assuming you have a "status" column in the CSV, how are you mapping the data in it?
-
What do you mean by "dynamic field"?
-
Have a look at the "notification scheme" for the project.
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/Mail-notifications-in-jira/qaq-p/579132
-
Add a new large text field (admin -> custom fields), add it to the screen and tab (admin -> screens) , then go to the field configuration and make sure the field has a rich text setup.
-
Ok, you'll need to tell us what the symptoms and error messages are.
-
No, if someone can log in, then they can use the functions that let them use Confluence.
-
A screen scheme tells JIRA what screens a field will appear on for a particular issue type. A field configuration tells JIRA some configuration details about the field when it is applied to an issue type - mandatory, type of input, and also if it is hidden.
-
Yes, you could do this, but it is a very bad design because moving the issue from a Service Desk project to a development project destroys the customer's interface. Imagine you raised an issue, went to chase it up and found it had been deleted. That looks ignorant and means you've got no way to apparently raise issues. OK,…
-
You could code for this, but it's not a good idea. Your developers and users are being lazy and, if I were being grumpy about it, ignorant. Issues should be moved to the "done" column when the people dealing with them genuinely think they have been done. "Meh, close sprint and just throw everything in the sprint to closed"…
-
I think you need to be quite careful here. While it's perfectly valid for people to have different accounts and want to merge them, it's just as important for people to be able to have more than one account and keep them separate. For those who want to merge, I really do hope there's something we can do for them. But don't…
-
You could do it with issue types, but it sounds more like you need a field you can stick on an issue to capture these categories. Components spring to mind, but these are very much project items, and ones that your project owners would be able to amend, so I think I'd look at creating a globally available select list for…
-
Which application is this?
-
JIRA doesn't have a chart like that. You could try the "filter statistics" one to get close though, or for a completely accurate one, a "2d stats" with one axis for issue type and the other organisation
-
What does the bottom of the log file say? You can get this if the Tomcat is running but the application is not. Check the confluence log file and catalina.out
-
A listener is too late. It's not quite this technically, but think of the process: * User clicks something to edit/add/remove a version * User clicks commit to their change * The version data is changed in the database * A version updated event goes out * Your listener would pick up the event, and, um, what? It can't…
-
No, just round it up. To start with 100, you need to create 99 dummies.
-
The project type is not a strong indicator of what the project is for, it's most important when creating a project, as it sets up stuff dependent on type, but after you've created it, you can make changes to the project that make it look a lot more like another type of project (and even change the type later) So, question…
-
You are going to need to explain that properly if you want an answer here, it does not tell us what you have done or what has gone wrong beyong "I've made a mistake I need to reverse". What's "finished future"?
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/Groovy-No-signature-of-method/qaq-p/578284 which has more information.