Comments
-
Actually, for the "people" section, it's easy. Use custom fields of type "user picker", and the system will place them there automatically. Frankly I wouldn't bother (and as for javascript - don't. It's a nightmare, and decent Jira admins remove all javascript whenever they can)
-
Yes, you can do reporting.
-
There is one that can strip text off, give that a try!
-
Yes, as long as the Exchange server has been set up to support the protocols of IMAP or POP (not the less functional MAPI that Microsoft favour)
-
That means you can't reach a server over your network and/or you've got the wrong credentials.
-
Excellent, then as long as they do not edit out the issue ID in the subject, then you only really need one incoming email address!
-
Yes, that's where I'd point you for instructions :-)You don't *need* one email per project, unless you do genuinely have a need to accept email for every project.
-
No. All the standard email handlers look at the subject of the email to see if there is a JIRA issue reference in it. If there is, they comment on the issue that matches. They don't care about the email addresses. The email address per project is only needed for the create issue from email, not the comment.
-
You should be able to go to admin -> look and feel -> custom html, and add a <div> to the header.
-
I think you've got a damaged database there. I'm not sure there's a way to recover it either. Howver, work your way back up the log until the first error and check what that says, it might have a better pointer.
-
Ah, yes, that would explain it.
-
Do you have full read access to the space you're pulling from? What happens if you just put the space key in without the selection choosing one?
-
What problems are you having with it?
-
Check the "conditions" on the close workflow transition. I suspect you'll find it says "must have resolve issue permission" as well as "must have close issue permission". If you're on more recent versions of Jira, you will also need to ensure they have "transition issue" permission.
-
You don't, the concept is a nonsense. The plugin does not do anything that can be "granted access to", all it does is add functions that can then be called by workflows (as edited by your administrators)
-
Can we ask what was wrong in the end? Some javascript you'd been messing with? A plugin?
-
I'm sorry, but "unable to select a value" is still not quite descriptive enough. Why can't you select a value? Is the list populated? Greyed out and unclickable? Select something and it doesn't save?
-
Ok, what does "not active" mean? Do they not appear in the list at all? Having asked that, I actually suspect you've got the "context" wrong. You can define a select list, with several possible sets of options, and say "use set 1 for project A, set 2 for project B, set 3 for project C" and so-on. My guess is that you've…
-
You'll need to give a lot more detail here. We have no idea how you "added various options", what you've done with the view, how you've configured it or anything else. It's not even clear whether this is a standard field, or one you've written yourself. Even "the values are not active" is not very helpful in describing…
-
Modify your permission scheme so that it includes the new group with *only* browse permissions Put your external users in it Remove them from all other groups and roles *except* jira-users (or they won't be able to log in) You could run into problems if you are using jira-users for anything more than "person can log in".…
-
There's no simple way to do it, and certainly nothing built in. Your best bet may be SQL
-
Bother, that rules out my initial thought on what might be wrong. I must admit I'm now a bit stuck, because I can only think of one way of surpressing the "required" flag, and you've just ruled it out.
-
Could you check if you have "allow unassigned issues" on or off in Global Configuration?
-
Go to the project and have a look at the admin page for it. Look for the "issue type scheme". You should be able to click through on to that if you're a jira-admin, and that will present you with a screen where you can drag your new issue type from the global list into the "available" list. Once you save that, "create…
-
There's no way to do that in the permission schemes - a user can either assign an issue or they can't.
-
There's no way to do that in the permission schemes - a user can either assign an issue or they can't.
-
I'm still not 100% sure I understand, but it sounds like what you want is to stop Bob reassigning the issue to someone else. Have a look at the permission scheme - you need to modify it in a way that says "Bob is not included in the people who can assign issues in this project"
-
I'm afraid that is not a clear sentence. So you want to set it up so that only the assignee can reassign an issue to someone else? Or do you mean you want to stop people assigning the issue to anyone but themselves?
-
You'll need to check and remove their "roles" too. If a user has "browse" permission because of a role that they're in, they could still get emails, despite being removed from all groups.