Fazila Ashraf Community Champion

@Deborah Sanderson , the favicon that you see on the tab is common for your jira site. You can update it as documented in https://support.atlassian.com/jira-cloud-administration/docs/configure-the-look-and-feel-of-jira-applications/ but it cannot be different for different projects.

@Stanislav , i would check this also..

@Stanislav , from my experience it is always the permission. You have mentioned that the board is scoped only to one project and the user has manage sprint permission to that project. If that was the case, the error wouldnt appear. I would advise you to double check and also have another user try the same with the same…

See https://scriptrunner.adaptavist.com/5.0.6/jira/jql-functions.html#_releasedate on the usage

@Stanislav , the permission scheme being shared with other projects shouldnt impact. Can you try with a different user? Are all the users facing the same issue?

Put the date in format 'yyyy/MM/dd' as mentioned in the error - 2021/12/21

yup.. fixVersion in releaseDate("before now()") would work

@Stanislav , what is the filter query? When you run it in issue navigator, does it return issues from the DL_...&_DevOps project only? Can you specifically add the user to the 'manage sprints' permission of the project (other than inheriting it as project lead)?

@Contexys , if you have scriptrunner, you can use the function like fixVersion in releaseDate("before 2021/09/02")

In the board's configuration, can you check how many projects are listed in the board's filter? A screenshot of that section would be helpful to guide further

@Suma Pralhad Kustagi , does it happen only in the board or in the issue navigator also? When the user searches in the advanced search for "assignee=currentUser()" , does he see the issues?

@Stanislav , can you translate the error message and share it? You should have the manage sprint permission for all the projects that are included in the board.. do you have?

1. The screens cannot be different for different user groups. 2. Refer to https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html -> Configuring a screen's tabs and fields. You can remove the fields from one tab and add to another. In the view screen, certain system fields like fixversion, labels,…

@Leo Epstein , if the normal user is the reporter who creates the ticket, edits it , comments on it, you can simplify the create screen to have only few fields. If the power users are the ones who works on the ticket, then you could have the additional fields during the status change transition screens. Another option…

Hi @Leo Epstein Ofcourse, You can reduce the fields from the screens. Are they complaining about the number of fields on the screen or the layout itself?

-2w = after 2weeks. status = "Waiting for customer" and not status changed after -2w => Currently status is waiting for customer and the status is not changed after last 2 weeks

The experimental methods could be changed in future, i wouldnt recommend using them in critical production setup

@Jodie Maczek , then you could filter on the status changed date some thing like status = "Waiting for customer" and not status changed after -2w

@satheesh , @Channa patna -> https://docs.atlassian.com/software/jira/docs/api/REST/8.15.0/

@Jodie Maczek , can you change the schedule to 1 day and check? For a daily schedule, what ever tickets are not updated in last 2 weeks from that day will be actioned on.. When you run in every 17 days, that would make many tickets wait for more than 2w.. When you run the search query in the issue navigator, how many…

Hi @satheesh If the APIs are specific to software functionality, you wouldnt be able to use it in the JSD instance. However, The JIRA core rest apis should be available for JSD also

Hi @Jodie Maczek Something like this? What did not work for you?

Hi @Natalia M. Looking at JQL functions from Scriptrunner https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_worklogged and JQLtricks https://www.j-tricks.com/jqlt-worklog-functions.html i do not think it is possible by status. I does support date range though. Have you looked at advanced reporting tools…

@Tobias , referring to https://confluence.atlassian.com/jirakb/how-to-upload-custom-priority-icons-in-jira-788961156.html Are the below conditions met? In order to view the icon correctly, both condition below should be met: * The issue where the icons are uploaded should be accessible by all logged in Jira users * In the…

@Michal Patoprsty , no. We actually tried it and the server license was not accepted in parallel with the JSW data center license. In server only, it is a single node deployment. In DC, it can be single node or multi node deployment. 

@Hans Meijer , in your case it is duedate but in my project, there was date custom field that the project team was already using to mark the end date. It was that i had copied over

@Hans Meijer , i was in the same situation and what i did was - using the scriptrunner's scriptlistener, i scripted that when ever a ticket in the project is edited, copy the 'custom date' field to 'target end date'.

Glad that it helped.. You can choose to "accept the answer" (at the top) to help the other users with the problem reach the solution easily.

@[deleted] , so for JSM, you have reached the 3 user agent license. Disable the 'New users have access to this project' flip in the 'Jira service management' section and this problem should be resolved

Yes, and then you can start your migration with the restored instance as your source.