Would anyone know how I can get the actual value of Tempo plugin's "Account" custom field and not just the index with script runner?
issue.getCustomFieldValue(Account) returns the index and not the value.
Meaning, if I have 3 entries(Bilka, Føtex, Meny) and the value is set to Føtex the above call returns 2.
it is simple, just add the assignee field to the workflow transition, for example when issue moving from New -----> Working, add the assignee button on working transition screen!
Thanks, that's sounds about right, but can I hide the Assign button from the view issue screen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
do you know if hiding the Assign button is possible?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you can try with following JS by adding in announcement banner
<script type="text/javascript">
jQuery(document).ready(function($) {
JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e,context) {
hideAssigneeOperation();
});
hideAssigneeOperation();
function hideAssigneeOperation(){
var projectName = $.trim($("#project-name-val").text());
var issueType = $.trim($("#type-val").text());
if(projectName == 'JIRA' && issueType == 'Defect')
$("#assign-issue").hide();
else
$("#assign-issue").show();
}
});
</script>
if it worked then i suggest to remove the code from announcement banner and load it as webresource module in a plugin, for your reference check this
https://developer.atlassian.com/display/JIRADEV/Web+Resource+Plugin+Module
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's really not a simple change. The "status buttons" are not performing simple actions, they're triggering movements of an issue through the workflow, which means conditions, validators, screens, post-functions, and so-on.
To take the simple action you've suggested - you want to go from "in progress" to "resolved". Specifically, how would you handle the screen this transition needs to present to the user to gather resolution information?
Two options spring to mind
1) A hack to remove "assign" from the options on an issue, forcing people to use transitions if they want to re-assign issues
2) Use a listener to catch "issue assigned" and perform the relevant transition when people do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks but #2 is not that easy since not all statuses have a predefined assignee.
I will think it throught. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.