Alexey Matveev Expert

I guess, you would need an add-on for it

These buttons are configured in the workflow, which is used for the Sub-task issue type. If you open the workflow you will see transactions with names "Open", "Close Issue" and "Resolved". Click on one of them and you will see the Conditions tab. Have a look there. There must be a condition, which hides the buttons. You…

You mean that one of the subtasks has a field and the other one does not have a field. How do you know which subtask must have the field and which subtask does not need the field? By a value in a custom field?

So, I guess you want to clone and move an issue. Unfortunately, I can not help you with it.

You can find an answer here: https://community.atlassian.com/t5/Marketplace-Apps-questions/Script-Runner-Example-for-Clone-issue-post-function/qaq-p/360406

I was able to do it like this string format = "yyyy-MM-dd" interval interv = #{number field Name} * 24*60*60*1000; // number to days date resolv = #{date field Name} + interv; // add interval date curDate = currentDate()+"2d"; // add 2 days to the current date if(formatDate(resolv, format) == formatDate(curtDate+"2d",…

Что-то в твоей Jira настроено. Как создаются запросы? Какие плагины установлены в Jira?

Да, такого не должно быть. Это значит, что где-то что-то настроено

How did you configure it? Did you add the Time tracking field on the create, edit or view screens?

@Fazila Ashraf thank you. I guess it is Jira Cloud feature

Just to make sure that I understood you correctly. You mean that you created a new project and added a couple of issues. Users from the old project can see issue from the new project. Am I correct? If so then you should change the project permission scheme. There is a permission called browse issues. You need to grant this…

I do not understand what you mean by "we have set field value as default date". How did you do it? In what menu option? I guess you need to change the field to the current date automatically in a post function for each transition. You can read more about it here:…

What do you mean by regular CSV import? I guess it is the same.

You could go to Issue Navigator and type a JQL query like this sprint = "Your Active Sprint" Then use export functionality to export all issues to a cvs file You can read more about exporting issues here: https://confluence.atlassian.com/jiracoreserver073/working-with-search-results-861257284.html

I was able to do it with the following validator script JFieldChange[] changes = getFieldChanges(key, "duedate"); JFieldChange latestChange = changes[size(changes) - 1]; if (!isNull(latestChange) && dueDate != latestChange.newVal && !hasInput("comment")) { string errMessage = "enter comment"; return false, errMessage ; }…

How do you create sub tasks? Sub tasks can not be crated before the parent task, which means, that the code I gave you is triggered not for a subtask, but for the task. Make sure that the code is executed for a sub task.

You can use status changed to closed after startOfWeek()

Try to use hasInput() function in a validator. You can find more info here: https://confluence.cprime.io/display/SIL/hasInput

I guess you need to check the Only licensed users who have access to the space checkbox

You should open each type of scheme in the coq item -> issues. For example, I attached a screenshot with worflow schemes for my Jira instance: You can see in the screenshot in which project my workflow schemes are used. I do not have shared configurations that is why there is only 1 project for each workflow scheme. If you…

the problem is with the last line. I guess, you pass a null for a parameter. Could you log.error (projectLead) and log.error(curIssue) and have a look in the log, if they are not null?

You can not see which project uses which project shared configuration. When a project is created from a shared configuration, behind the scene Jira just apply all schemes (workflow, field, permission, screen and so on) to the new project. After it you can switch any scheme to any other scheme in the new project and your…

I am also not sure to whom to submit. The problem is that many tutorials were out of date in the documentation but I noticed that recently Atlassian began to fix it. And the documentation became better. 

You would need to name a release with a component prefix and connect each release with issues of a certain component. Out of the box this connection can be made only manually. 

I attached a screen shot:

It is not possible.

I guess you need to download a javascript with your panel which would do all the job. It will make ajax calls and fill up the necessary fields.

Kindly read the following KB https://confluence.atlassian.com/jira064/configuring-issue-table-columns-720412300.html

I guess, it means that the new owner does not have browse issues permission for the 10800 project.

You should configure the assignable user permission in the project permission scheme. You can grant this permission to a role and define different users for the role in each project. You can read more about how to manage permission schemes here:…