Comments
-
Hi Eitan, You can also use different screens to control what users can do - but it is global, not per person. For instance we use a different screen for Create, Edit and View that allows users to create but not edit a field. But they can still view the field. If users are savvy, they will figure out they could change it…
-
Hi Michele - So if I understand the problem correctly, you are trying to assign an issue to either Brian or Eric or Robert - but not all of their names are showing up. Correct? Can you do a screen shot of the issue with the assignee field - maybe typing in the first few letters of Robert (like Rob)?
-
Happy to try to continue helping. Not sure I understand exactly what is going wrong where though. Is it that you cannot assign a ticket to someone because they don't show up in this list of people to assign a ticket to? Is the person Active in the system? Or are you experiencing another problem?
-
Hi Michele - I would start with making sure you have the right Permissions Scheme attached to the project (under Project Settings). Make sure the Permissions Scheme is attached to a role you have on that project for Assign Issues in the Issue Permissions section.
-
Yes, there are lots of options for populating other fields. For example, we use it to clone a recurring need ticket and set the Due Date on the new ticket to be a month out or a year out or whatever.
-
We use the JMWE (JIRA Misc Workflow Extensions) add-on to perform that function. And you don't have to write code!
-
We handle it through the permission scheme for the project where the Browse Issues is only granted to project roles.
-
Hey JT, We simply include the statuses that map to the columns on different boards. For example: Board A has columns 1, 2, 3, 4 in the workflow. Board B has columns 4, 5, 6, 7, etc. in the same workflow. As the issue gets to column (status) 4 on Board A, it automatically appears on Board B also.
-
Anybody know if there are plans to put Roadmap in existing (non-Next Gen) projects?
-
It would be great if there was a link for each of the 10 items above that went to documentation on how to implement the new features or specifically how they work.
-
Awesome - thanks, @Gabriele Franck!!
-
Hey @Gabriele Franck - looks like that feature request was closed by back in January and you can't vote for it.
-
You could also do a subscription off of a filter to send at prescribed times.
-
@Jagannath Reddy - another option is to do a Subscription off of the base filter used by your gadget.
-
All, I ended up putting in a support ticket. We were able to get accomplished what I wanted by using a Validator for the transition. Shout out to Ricardo Gebhardt for his excellent assistance! John
-
Yes, it works on issue search, but not in the transition condition of the workflow.
-
Thanks, Syauqi! And that's very interesting about it only be linked to the filter with the project in it - very helpful. We have some boards that are simply based on a filter for a particular Epic. Always wondered how JIRA knew which statuses to put towards the top in the list of statuses to the far right. Thanks again!
-
I can already see what workflow is associated with the status. But a board is also associated with the workflow, too, not just the project. So it should be possible to connect those dots. Is there an open support issue for this?
-
Hi @Nic Brough -Adaptavist- - Does this prevent the user from updating the field using the Bulk Edit feature?
-
Thank you for the reply. Is there anyway to see a list of ANY Invalid filters?
-
It sounds like you have yourself in somewhat of a loop. You can't add a person to My Watcher because they are not in the Security Level. And the Security Level is granted to My Watchers. But the issue seems that the person is not already in the My Watchers so they can't be added to the My Watcher. I usually assign Security…
-
Thanks @Maarten Cautreels - I voted for the link above. Unfortunately, the JQL Tricks Plugin is not available for Cloud, which is what we use. :-(
-
@Maarten Cautreels - anyway to do a query to see what issues changed from a particular issue type to another type on a particular day?
-
No, Power Scripts is not available for Cloud either. :-( So, there's a bug in JIRA and we can't get around it with an add-on because none exist for the Cloud version to get around the bug. grrrrrrr
-
Behaviours is not available for Cloud. :-( Do you think Live Fields might be available for that version?
-
That works for Single Users, but not Multiple Users. There is no Edit User Filtering for User Picker (Multiple User) custom fields.
-
Very good - thanks for the quick reply.
-
Hey Nic - any idea when the Behaviours function will work for JIRA Cloud? Or any idea of another tool that will allow me to set the values of the Issue Type field based on the value of a custom field - in JIRA Cloud?
-
We had to add the Organization as a managed account. After that, I am able to change the Full Name - but it's a different path.
-
Figured it out and have it working if you are interested. Looks like this: <a href=<span>"http://jira.atlassian.com/secure/CreateIssueDetails!init.jspa?pid=10420&issuetype=4&&summary="A1&"&reporter="</span>&B4&></a>