Comments
-
I just checked searchers and I could not see any difference with a field display. Could you give more details.
-
I guess you would need to join customfield, customfieldvalue and AO_XXXXX_sprint.
-
You should check if the filter, which is defined for the board, returns any issues. If no, then you should change the filter query. You can find the filter in board configuration on the General tab.
-
I am not sure what Jira SDLC is. When you connect to your Jira do you have atlassian.net/ in the url?
-
You should push the get it now button from the link which I gave you
-
It is not possible out of the box. But you could use Power Scripts Live Fields or ScriptRunner behaviours to do it.
-
The add-on is available only for Jira Server or Data Center. You can download it from here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.keplercf/server/overview Then you should install it in Addon->Manage addons->Upload addon
-
You can find the answer here https://jira.atlassian.com/browse/JRASERVER-24522 Read the first comment
-
I guess the only thing you can do is to remove the required fields from the edit issue screen, make a screen with such fields and create a transition with the screen attached. Then you could use conditions to restrict the transition execution.
-
I guess you installed the Cloud version. Unfortunately, I do not have it in my Cloud and I can not help you with it.
-
You should add time tracking field to the create issue screen. Did you do that?
-
What do you mean by time tracking button? Could you provide a reference to the mentioned support document?
-
[EDITED] You add issues to a version by filling the Fix Version field. That is why if you want to forbid some users to add new issues to a version then it means that you want to restrict the ability to fill the Fix Version field for some users. You could delete the Fix Version field from the edit issue screen. Then make a…
-
You should go to the field configuration scheme for the project. I guess the Version field is set as Required. You can either mark it as not required or you should add the field to the screen. You can find more info on field configuration schemes here:…
-
You could use Jira Service Desk Rest Api to create requests. You can find more info here: https://developer.atlassian.com/cloud/jira/service-desk/rest/#api-request-post
-
Maybe it could work like this Issue updatedIssue = issueManager.updateIssue(user, issue, UpdateIssueRequest.builder() .eventDispatchOption(EventDispatchOption.ISSUE_UPDATED) .sendMail(false) .issueProperties(new HashMap<>()) .build()); But I did not try it.
-
Try write in your js just alert("hello"); to make sure that it is not loaded. I never had problems with it within Jira. Through I do not use the announcement banner anymore.
-
You can make a custom field which would calculated the age of an issue. You could use Adaptivist ScriptRunner or Power Custom Fields. Power Custom Fields is a free add-on. You scripted field would have a script like this. return (currentDate() - created);
-
You can find an answer here: https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-get-current-project-through-javascript/qaq-p/468007
-
What version of Jira do you have? Is it Jira Software? How did you create a basic software project? There can be something wrong with the Jira Software functionality. Kindly have a look in the atlassian-jira.log for errors.
-
You should add the Fix Version field to the create, edit and view screens. You will be able to link a version to an issue using this field.
-
There is Jsincluder plugin which will let you add your javascript file to the create, edit, view and transition issue screens. https://marketplace.atlassian.com/plugins/ru.mail.jira.plugins.jsincluder/server/overview
-
If you have Power Scripts add-on, you could write a JQL function which returns no more than 20 rows.
-
You should create a board. You can find more info here: https://confluence.atlassian.com/agile/jira-agile-user-s-guide/creating-a-board
-
Do you mean that the sandbox project is in the production Jira instance? I think you should have at least 2 Jira instances. One for sandbox and one for production. You can transfer configuration using Adaptivist Project Configurator or Configuration Manager plugins.
-
You should create a usual custom field, not a scripted field. And then fill it in the post function which you use for creating issues from your workflow. How do you create issues from the workflow? What plugin do you use?
-
Just create a plugin. You can find a tutorial here: https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/ There will be resources in the atlassian-plugin.xml. Add jira.create.issue to the context tag. The context tag defines when your resources will be downloaded.…
-
Better write an add-on with your JavaScript file. It is not that much difficult.
-
You can use Jira Rest Api. You can find more info here https://community.atlassian.com/t5/Answers-Developer-Questions/Issue-history-through-REST-API/qaq-p/503830
-
Rest Endpoint is situated in the server side. It can not know information about the page which is viewd by a user in his/her browser. That is why you need to pass the issue key.