Comments
-
I don't think you do - I assume you're using JETI? You'll need to raise an issue with them (although I have a nagging doubt that they do actually support this already)
-
If you're coding your own handler, then there should be, yes. I've not tried it myself, but I think it's possible.
-
You'd need to write a plugin to add the facility to tag comments (which, I don't think is an easy plugin to write), and you'll need to re-write the "email this issue" function as well.The significantly easier option would be to write a new email handler - one that essentially duplicates the current behaviour, but also has…
-
No, a comment is a comment, there's no information stored about how the comment was made. If you want to distinguish between them, you'll need to code for a flag on the comments, and add something in the "email this issue" plugin to set the flag. If it's just about the notification and the information about how it was…
-
You can take the url and try changing the "tempmax=X" part of it, but this can be blocked by your Jira admins to prevent you damaging the system. There's a good reason for the limit - the export is intensive work and can take down your system by overloading it. Generally, a better question is "why are you doing the export,…
-
I agree with Geert here, although I'd phrase it slightly differently - Instead of looking at Jira Agile and asking for "best practices for Agile although we're not Agile", it would be better to look at your process first. It's not a case of using Agile because you can, I think you need to think about what you need from…
-
A cursory glance or search would have led you to https://support.atlassian.com for help with Cloud installations. Also, you might want to look at what you're entering, as I don't get this behaviour on the Cloud install I'm using.
-
Ok, there's no "export" of these. But it's quite easy to extract - go to an issue where you can edit the field (or a create. Or the screen that lists the options in Admin), hit ctrl-s to save it and then scrape it out of the plain html. ( html2txt is rather handy if you're on a useful operating system)
-
Arg. A select list custom field has a list of options and data associated with issues. Which one of these are you looking for?
-
Again, do you mean you want the data that you habe put on the issues, or the possible options for the select list? They are different things.
-
Dou you mean the options available, or the data on the issues?
-
Because they are different. Components are a sub-set of project data, and their names are nothing more than labels. If you looked in the database, you'd find each component is a separate, discrete entity with a different ID. It helps a little if you think of a component as being a project/component pair. Although you're…
-
I won't ask why - I've been there. I find it rather amusing that there was loads of noise about it, I added the filters asked for and 3 months later no-one was using them because the standard ones were working fine. I quietly replaced their useless filters with a handful the noisy users had never mentioned and got lots of…
-
No but yes. No because you can't do it in the UI, you need to indulge in some coding. But yes, because the coding isn't that hard (although it's well buried in the docs, the searches I tried didn't find it) - https://developer.atlassian.com/display/JIRADEV/How+to+create+a+custom+preset+filter That covers adding your new…
-
To be a reporter in JIRA, you need to give them JIRA user accounts. I'd add them to a user directory. They could go into your LDAP, but if you don't want to do that, you could set up another LDAP directory for them (or other type of directory) or even just add them to the internal directory. You'll probably want a script…
-
Restricted spaces are easy - just don't add the users you don't want in them in the permissions. You can't hide from your admins though. They don't have to be part of the space, but admins can always see spaces and amend the permissions to let themselves in. You have to trust your admins.
-
I've seen exactly the same - you have to shut down Jira cleanly well before you reboot or HSQL gets corrupted. You might be able to rescue the database with a little inventive hacking, but there's a good chance that even if you can get back in, you'll have lost data. As Dieter says, HSQL is not suitable for production…
-
Happens to all of us sometimes. Have a look at https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html
-
Ah, I see, you're not quite seeing how the field works.You need to add an option to the list. Then leave the default unselected. That will give you a single, unchecked box on your screen, which the user can check if they want.
-
That's fine, it's telling you that you have not set a default
-
Yes, leave the default unselected. You'll get your list of checkmarks with their names and none of them selected
-
Log in as an admin, go to Admin -> issues -> issue types. Click to add a new issue type. Now go to the issue type scheme for the projects you want to change, you will be able to add the new issue type to them. Finally, go to the workflow scheme - you'll find you can add a new workflow to it and select the new issue type…
-
If you have no admins to ask, you'll need to raise a support call with OnDemand support to get your administrator replaced (presumably they left your organisation and didn't sign anyone else to the group).
-
Um, ok, I'd assumed that Teilor's (correct) answer had covered this 15 months ago, after you had clarified that you did mean "re-ranking an issue in the normal way". I hope you didn't wait 15 month though, it really shouldn't take that long!
-
Could you explain "Moving any issue in the same column from below to all the to top on an agile board " - that makes no sense - I cannot imagine what you are doing beyond picking up an issue and dragging it to... um...
-
You cannot poke in a password - JIRA has the more secure model of storing a password hash, so the password is not retrievable. You must poke in the password hash. If you use the hash given in the documentation you have found, you will also find that the password you can use is listed on that page ( sphere ). Once you can…
-
Ah, good, then I think you just need to tweak the watcher != bit. I think that is being read as "the watcher is not the current user". Looks right at a glance (and it completely confused me on my first comment too), but thinking about it, I think that will only match cases where the current user is the *only* watcher. I…
-
Um, I'm stuck. You say you want to find issues where you are not a watcher (before the JQL, which, incidentally, looks like it should work), then say that it's returning issues where you are not listed in the watcher field. That sounds correct? I suspect a typo here?
-
duplicated by https://answers.atlassian.com/questions/45965230 raised 10 minutes later, but has a bit more detail.
-
Sorry, I really don't understand what you're asking for? Do you mean you want to prevent users entering more than a certain amount of text in comments?