Comments
-
If that user can see the page they are mentioned on, then they should be emailed (after sync)
-
They will only send mail to people who have permission to see the page they're being mentioned on.
-
Yup - the options are great, there's no need to have Jira admins have to maintain the lists. But adding the core field is definitely a central thing. Hey. Pays the bills though :-)
-
Indeed - there should be a field type that says "this is a project field, list of options to be managed by the project owners". I'd shy away from allowing project owners to define their own though - a good chunk of my career has been "clean up the mess made by allowing PMs to add their own fields/workflows". I'm not…
-
Nope, as C. Faysal says, it's not possible. You'll need to write or find custom fields that support this sort of thing. I'm not actually aware of any in the marketplace, which is a little surprising as I can see the use for them.
-
Ok, that makes sense. The problem now is that you're expecting the gadget to be configured with information you are not giving it. You will need to refine your filter to report on what you actually want. Doing a secondary selection on the gadget level is quite a lot of complex coding you'd need to add, and it's inefficient…
-
>JIRA supports Multiple values of field Test Case Status You'll need to explain how it is doing that - is it a multi-select field or something else? Something coming from an add-on?
-
There is no field that does this natively. The "updated" field is populated by changes, but those aren't all drawn from the same place - Jira updates it as part of workflow or edits (see the table changegroup) and comments (table jiraaction) and I think there are probably other places. It does not copy out who made the…
-
Yes, there are ways to do this. Look for add-ons that match your CRM in http://marketplace.atlassian.com to start with.
-
Very quick answer because it sounds like you just need a spot of help getting there... Go to Admin -> Workflows. Edit a workflow (if you don't have any custom ones yet, then you'll need to create a new one. As you're new to workflows, I'd recommend copying the default one) Once you're in the workflow, look for it's…
-
I don't know if JIRA bots might appreciate being called "slack"
-
Yes, but only in a broad sense. If you use the special group "anyone" in the permission scheme for a project, you enable anonymous access, which means people can use the project without logging in. That solves the problem, but there's a couple of big warnings on it * Only use it for browse project (and maybe 'view…
-
It's quite difficult to do this natively, most people use plugins that provide listeners or post-functions to capture the events, check the priority (or other data) and then send attitional emails on top of the standard notification schemes. The closest I've got without coding was to have custom field for priority, which…
-
Ok, before you do, a "calaculated text field" is not a standard function, it's being provided by a plugin somewhere, and don't know which one does it. I'm only really familiar with the hard-coded ones I've written, and the script runner, so I kind of need to know which plugin it is so I can skim the docs (I know roughly…
-
How are you doing the "custom calculated text field"? With the script runner, a plugin or something else? As it's a calculated field, I'm not sure why you're looking at the default value as the default value won't matter if you override any entered data with a calculation. Whatever you answer, the response is going to be…
-
It's global. There are a few requests around making it project, but it's global at the moment.
-
That would do it :-)
-
Check the permissions page - exactly what groups have "use" and "administrate" permissions?
-
Ok, there's a few more options here... Script runner won't do it, unless what you want to do is put a normal date field on edit screens and then write a scripted field that displays the MMM-YY format you want on view (and search) Another option, if you don't have too huge a range of dates to worry about might be a…
-
On 4 - google is most likely to give you "write your own add-on to do it..."
-
There's a tick to the left hand side of the answer to allow you to mark it correct - Answers will stop reminding you about it if you use that.
-
Add the field to the screen. https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens
-
I'm sure it's on the improvement list somewhere...
-
Um, I'm not sure where you got the idea that the project setting was a "default"? It's not a default, it is where the issues go. Andy Brook's JEMH does parse for project (if my memory is correct), but that's not installed OnDemand, so it only has the functions as described in…
-
This is quite complex, JIRA is built to hold issues in one project, and moving an issue is not a trivial task. This is because the project is where all the configuration is held. You can easily create two projects that are totally different - different fields, screens, notifications, permissions, and most importantly,…
-
Ahh, Comala workflows, handy add-on that It's the same answer though - you need to look at each workflow individually.
-
You've asked about Confluence in most of the question, but then asked "where a group is used in permission schemes and workflows" Confluence does not have permission schemes or workflows. Those exist in JIRA. So I'm questioning what you're asking about (because the answer to your question as written is "there isn't any")…
-
Confluence doesn't have those, do you mean JIRA?
-
If you use the log.debug to spit out the content of issueLabels after you ask the issue for all the labels, do you get anything in the log? (If you do, it'll probably be ugly to read, but it might tell us something!)
-
It's always best to use the Tomcat that is bundled with your target version of JIRA.