Comments
-
Project Admins can not do it. Only Jira admins
-
You should look for an add-on. For example, Nfeed
-
It is not possible. The standard cascading select list does not support multi select.
-
You would need a plugin for it like Power Scripts, ScriptRunner, Automation for Jira.
-
You need to transition the issue. Kindly have a look at the code here: https://community.atlassian.com/t5/Marketplace-Apps-questions/Groovy-Script-for-Linked-Issue-Transition/qaq-p/17706
-
Kindly find the JQL query, which is defined for the board (General tab in the board configuration settings), and try to execute the JQL query in the Issue Navigator. If you can not see the results, it means that you do not have the browse issue permission for the issues, which the JQL query must return.
-
Then you should to try to troubleshoot your outgoing mail. You can find more info here: https://confluence.atlassian.com/jirakb/mail-and-mail-handlers-troubleshooting-211649643.html
-
Did you make changes to the project notificaiton scheme? You should add users, who must recieve notifications, when the event is fired.
-
It is possible. You would need a browse permission for the two projects and the Link Issues permission. Then you can create a link between two issues. You can find more info here: https://confluence.atlassian.com/adminjiraserver073/configuring-issue-linking-861253998.html
-
Just try it. I guess, it should work. If you choose Backbone Issue Sync then you need to do setups. If you choose Power Scripts or ScriptRunner then you would need to develop scripts. Kindly start with Backbone Issue Sync and have a look, if it works for you.
-
You mean on the same server or on the same instance? Anyway it would work fine
-
Backbone Issue Sync can work on the same server. same with Power Scripts and ScriptRunner
-
Let me clarify a bit on what you want. Let s say you have "TEST_FIELD" custom field. On Jan 28 you set the "value 1" value for the field. Then on Jan 30 you changed the value to "value 2". On Feb 1 you want to write a JQL query so, that in the issue result view you would see the value of the TEST_FIELD on Jan 28? You want…
-
The only way to restore a ticket is to use a backup. But you can do it only if you backup your Jira instance. If you do not have backups, then you can not recover the deleted ticket.
-
It gives you one month later, because you add 30*24*60*60*1000, which is 30 days after the current date. You should do it like this: def csDate2 = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Approved On") Timestamp csDate1Value = (Timestamp) issue.getCreated() Date csNewDateValue = new…
-
It is not possible out of the box. You need an add-on like Power Scripts or ScriptRunner.
-
What do you mean by startDate of an issue? Do you mean the createdDate? If so, just use GET /rest/api/2/issue/{issueIdOrKey}
-
You should login to Jira as and administrator. Go to Issues -> Custom field. Find the field for the Select a field custom field and configure the field.
-
Click the magnifying glass in the upper left corner:
-
What do you mean by switching between remote repository and origin? Origin is the default name for the remote repository.
-
It is only for Jira Software.
-
You would need an add on for it like Power Scripts, ScriptRunner, Automation for Jira.
-
Add the field toto to your behavior and add your script to the filed.
-
If it is ok with your requirements, then it is a cleaner solution definately.
-
Better create a validator. If resolution is entered then throw a error. I think it is a better solution.
-
You should add a validator to the transition, which will check that the resolution field is not empty/required.
-
What do you mean in your role? It will show only users, who are granted the assignable user permission. Make sure that the users you are looking for are in the assignable user permission either through a group or a role.
-
Hello, Kindly have a look at the Backbone Issue Sync pugin. It can synch statuses from different Jira instances, maybe you can make it work for one instance.
-
It is not that simple to change an issue type, because issue type influences many other things like screens, workflows and etc. You can use ScriptRunner to write a post function, which will change the issue type.
-
Ok, now I understand the question. No, it is not connected to business project. Kindly check that your user can see issue in the business project and the filter for the board selects issue from the business project.