Good day!
I have created a very small Kanban project that only has 5 statuses (Backlog -> Selected For Development ->In Progress -> Done -> Archived)
the issue is that only I am able to execute the transition from Done to Archived but the user who will be using this board is unable to Archive tasks. The option does not show for him
Is there some user level setting or permission I need to add for him in order for him to be able to archive tasks? is it permissions I need to set on the transition? if so any steps will be greatly appreciated!
Thanks in advance!
you add the statement
ComponentAccessor.getIssueIndexManager().reIndex(issue);
at the end and check.
Hi,
I realized there is some issue with this line:
issueManager.updateIssue(componentAccessor.jiraAuthenticationContext.getLoggedInUser(), issue, EventDispatchOption.DO_NOT_DISPATCH, false)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I think componentAccessor.getJiraAuthenticationContext().getLoggedInUser() would be there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you tried by adding reindex code ?
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.
where you are adding this code?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check setFieldValue method here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've had a problem with multi-select fields (from what I gather that's the type of your field), where we couldn't filter the information by their values. The way I fixed it is, I made the multi-select field behave like the default Component field in Jira (i.e. add lables for each option). I did that by adding this JavaScript to the description of the multi-select field:
<script type="text/javascript">
(function($) {
// "customfield_10400" is the number of the custom
// multiselect field you want to change as e.g.
// seen at the end of the "configure" page url of
// the field you want to change this way
AJS.$("#customfield_10400 option[value='-1']").remove(); //Removes the default value "None"
function convertMulti(id){
if (AJS.$('#'+id+"-textarea").length == 0){
new AJS.MultiSelect({
element: $("#"+id),
itemAttrDisplayed: "label",
errorMessage: AJS.params.multiselectComponentsError
});
}
}
AJS.toInit(function(){
convertMulti("customfield_10400");
})
JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e, context) {
AJS.$("#customfield_10400 option[value='-1']").remove();
convertMulti("customfield_10400");
});
})(AJS.$);
</script>
After that everything worked like a charm.
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.