Alexey Matveev Expert

Из коробки нельзя. Может быть, есть какие плагины, но я таких не видел.

I guess you use the Tempo Timesheets plugin. There is a function to close a period. I guess the last week is closed. You have to open it. You can find more info here: https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785889/Period+management

I guess you use the Tempo Timesheets plugin. There is a function to close a period. I guess the last week is closed. You have to open it. You can find more info here: https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785889/Period+management

Suppose, you want to transition an issue to the In Progress status, if the issue has been in Penidng status for 5hours. Then you should create escalation service. Define JQL like this status = Pending and status changed to Pending before -5h Then in Action you should choose a transiton to In Progress status.

import com.atlassian.jira.project.Project import com.atlassian.jira.project.ProjectManager import com.atlassian.jira.project.AssigneeTypes import com.atlassian.jira.component.ComponentAccessor def originalproject = ComponentAccessor.getProjectManager().getProjectObjByKey("TESTOR") def name = "AAA" def description = "test"…

What do you mea by "set a task"? Do you update a custom field?

Yes, the name of variable are different from declaration and passing the the procedure. import com.atlassian.jira.project.Project import com.atlassian.jira.project.ProjectManager import com.atlassian.jira.project.AssigneeTypes import com.atlassian.jira.component.ComponentAccessor def originalproject =…

You can set a schedule task in scriptrunner either by escalations services or scripted services. https://scriptrunner.adaptavist.com/5.3.9/jira/escalation-service.html https://scriptrunner.adaptavist.com/5.3.9/jira/services.html

Нужно проверить, что ее никто не отключил. Вот здесь написано как https://community.atlassian.com/t5/Jira-questions/Work-log-tab-is-no-longer-visible-on-some-issues-how-can-I-get/qaq-p/405957

Да

Отключается поддержка этих плагинов и их обновление. В текущем состоянии система будет работать.

Unfortunately I do not have time right now. You should learn how to debug your code. 

Could you provide the log edit screen as a screenshot?

I did not check the code by it must be like this: import com.atlassian.jira.project.Project import com.atlassian.jira.project.ProjectManager import com.atlassian.jira.project.AssigneeTypes def originalproject = ComponentAccessor.getProjectManager().getPrjectObjByKey("TESTOR") def name = "AAA" def decsription = "test" def…

No, that is a screen of setting a custom field. You need to set the edit screen for an issue. You can find more info here: https://confluence.atlassian.com/adminjiraserver071/associating-a-screen-with-an-issue-operation-802592588.html

If you are not sure, then do not implement anything. 

You would need to write a validator to check the picked value by user. Or you can use behaviours.

run atlas-debug. Set breakpoint to createIssueType() and have a look. But I think the right was is to implement the InitializingBean interface and create the issue type in the afterPropertiesSet method.…

No, there is no limitation. It must work. Unfortunately I am on linux and I can not check it. But when I was on Windows, I set the parameters by "To set properties for Windows services via command line" and it worked.

issueFunction in expression("", "reporter == assignee")

What is the error?

Если по легальность этого действия, то я тебе не отвечу. Но если есть аккаунт в Jira и несколько пользователей знают к нему пароль, то они могут им пользоваться одновременно. 

You would need an add-on for it like Power Scripts, ScriptRunner

Most of the fields are available on the view issue screen only if they have values. If there is no value, then you can set a value for such a field only on the edit issue screen (the edit button) or in a transaction screen.

Do you launch your Jira instance by a Windows Service? You can find more info here on how to set the variables https://confluence.atlassian.com/adminjiraserver073/increasing-jira-application-memory-861253796.html

Statuses are defined the the Issue -> Statuses. If you use the same status in your workflow you will just inherit the name of the status and the order of the status. It means, that if somebody changes the name of the status, it will be changed in all workflows, where the status is used. All properties, which you described,…

I am not sure what happened in your local git. But you can always clone repostitory to a new folder and then update required files from the current local folder.

You need to pull first the branch from the repository. If there will be no conflicts, then your local code will be merged with the remote code. After it you can push your version to the remote destination.

You can see the whole list in the attlassian-jira.log

These errors are actually the permissions for the group)