Ignacio Pulgar Expert

Your Scrum board probably has at least one status not mapped to any columns. May you check it on Board > Configure > Columns? If that's the case, replicate the same status <> column mapping in your kanban board and, voilà! The same issue count should be expected. Hope it helps.

Do those two issues belong to the same project? Otherwise you might need to check the relevant permissions in both projects. If that's not the case, I assume you are trying to link both issues by clicking on More > Link from the issue detail view of one of them, aren't you? What's the point in which you cannot advance…

Then I'd open a help request with ScriptRunner Support: marketplacevendorsupport@adaptavist.com Should you find out how to fix it, please, post the solution here so that other community members with the same problem can obtain the correct answer here. Best regards

Reviewing the docs for Description: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html#_setting_a_default_description There's no need to select the fields, as they are implicit in the code. Perform the following actions, and try again after each of them: * remove the selection of both fields * (if the…

I like the purpose of this question (archiving old projects automatically after some months from last update on an issue) as well as Alexey's invaluable input.

So the question is: How can the Permission Scheme set on a project be changed programmatically? Is that correct?

Labels are a cool way for informally classifying issues, but adopting labels as a way for distinguishing types of issues here would negatively impact: * reporting * browse-ability of eligible values * and require-ability (bypassed by typing anything) So I'd discard this approach, given the description of this use case.

As a rule of thumb, you should only create a new issue type when that's the only technical way of applying a requirement, such as when the different kind of tasks within the very same project require: * completely different workflows, * to have a different selection of required and/or hidden fields, * distinct set of…

Is your user account inside the Administrators project role of the project France-Soir Wine Shop?

Hi Monique, Provided you have a backlog view, all you have to do for ranking an issue is a drag & drop on it to the desired position. Issues from your backlog are ordered this way to define the queue of "what's the next story that we should work on" as the top element. If you are working on a large backlog and want to move…

May you try this alternative line? def srd = getFieldByName("ServiceRequestDetails")

That action needs to be performed whenever you need more width for comfortably inline-editing the custom field. I personally prefer including all text in Jira's Description field, as adding custom text fields rarely adds value to the overall configuration of the app (no reporting on text field values, JQL searches will…

Cannot tell it with absolute certainty, but maybe the previous admin configured the anonymous user as per this KB article: https://confluence.atlassian.com/jirakb/unable-to-create-issue-due-to-anonymous-sender-and-no-default-reporter-224401408.html So, that user might have been created for setting it as the default…

Hi Sheila, You may enlarge the field to the desired size by clicking on the lower right corner, drag and dropping to resize it to get the best fit: Hope it helps.

By the way, the following blog post about Keyboard Shortcuts is worth reading: https://www.atlassian.com/blog/jira-software/4-ways-get-jira-keyboard-shortcuts

Good point, Jack.

Also review the workflow statuses properties. The jira.permission.create.clone.denied is known to break some calls to the API.

Glad you could finally fix it! :) Regards!

The Clone feature tends to lead to this and other kind of inconsistencies, like enabling the possibility of creating an issue with values that do not apply to the actual circumstances of the new issue being created. It's not a surprise that disabling the Clone option in Jira counts with its own How-To article. It is also…

Just delete the board you don't need anymore, as that action cannot impact the other board.

That's really weird. Let me ask you a few questions: * Do you have any user-installed addons for cloning issues? * Do you have Create Issues permission in the project where you are trying to clone the issue? * How exactly are you trying to clone the issue? May you add a screenshot? * Are there any errors being shown in the…

Is the affected agent under the Service Desk Agents project role in the project the request belongs to? Note that Service Desk might override some of your configuration in the Notification Scheme. May the affected agent double check the notification email has not been marked as spam, therefore skipping in the inbox?

Click on Boards > View all boards from the top bar. Find the board you would like to delete. Click on the ellipsis [...] button on the right side of the board's row, and then click on Delete: Hope it helps.

Thanks for the clarification. May you confirm if the agent currently has an active Service Desk Agent license?

Hi Alfonso, It is not possible to make a query return the results it would have returned in the past. That would only had been made possible by creating a Jira backup on that date and restore a testing Jira instance from it. However, it is possible to get all issues that were on a certain status on a specified date with a…

I think Alexey's point might be pointing to the solution here. Just for clarifying it: Was the issue initially created and, afterwards, assigned to an Agent? Or was the issue assigned to the Agent from the Create Issue screen?

Did the user assigned the issue to himself, or was it assigned to him by anyone else? If it was assigned by himself, that's the expected behaviour, provided that user 'does not get notified of its own changes'. That option can be changed from the user's profile.

Hi Stu, Provided that an issue (either Epic or any other type) can be displayed in multiple boards, the only feasible approach I see for the need you are describing would be: * enter the issue detail view * click on the 'View issue on board' link, under the Agile section: * Select the desired board Note that this feature…

Well, as long as it works, you may continue using it in the meantime, until you find a better alternative, as executing thousands of queries because of filter subscriptions every 15 minutes doesn't seem to be the most efficient way to go here. Service Desk counts with Automation Rules which can be set to add an internal…

Do all those 5000 users have a Service Desk license? Otherwise they won't be able to get results about SLAs...