Comments
-
Hello Lee, Do you mean to get select custom field options via REST? There is no such feature to get a single custom field option. Besides, the json you aforementioned returns all values including enabled and disabled, and it does not have indicator so you can not know whether the option is enabled or not. There is an open…
-
This discussion is a duplicate of https://community.atlassian.com/t5/Marketplace-Apps-questions/Getting-an-issue-back-to-Not-Started-removes-SLA-plugin/qaq-p/584193
-
Check the email format in global settings * Go to System > Default user preferences * Click the Edit default values button. https://confluence.atlassian.com/adminjiraserver/configuring-the-user-default-settings-938847012.html For individual user email settings, please…
-
Hello Ramesh, Hope this helps import com.atlassian.jira.web.bean.PagerFilter; import com.atlassian.jira.bc.issue.search.SearchService; import com.atlassian.jira.jql.builder.JqlQueryBuilder; PagerFilter<Object> pager = new PagerFilter<>(PAGE_SIZE); SearchResults searchResults = searchService.search(searcherUser,…
-
I'm not sure but I think you should use setCustomFieldValue. it.setCustomFieldValue(issueValue.getFormValue())
-
Try &customfield_id=<Team_Name> or &customfield_id=<Team_Id> Samples for customfield_id : customfield_10001, customfield_10103
-
Post functions?
-
Ok, please share the post functions of that transition
-
Kieron says, they can drag & drop which means it is not two statuses in the same column. By the way, I 100% agree that's poor design, we cannot drag and drop to another status in same column which can be pretty possible.
-
Hello Kieron, Actually, that is not the expected behaviour. Or I am missing something. You can drag the issues from a column and drop only to column that there is a transition to. Assume, - you have two columns A and B, and each have statuses A1, A2, A3 and B1, B2, and B3 - There is issue in column A with status A1 - There…
-
Hello Mark, The request is not clear on my side but I do not think there is a production-ready solution for this by using Atlassian products. You have to build your own plugin or use some Marketplace add-ons. For instance, you can use Time to SLA app to track time and/or use Script Runner for Jira to create a scripted…
-
Jira looks for Development Tools permission to see commits, branches, .. Are you sure that you have the permission?
-
All custom fields are stored in customfields table in Jira. Also you can find options and values in customfieldoption and customfieldvalue tables. Is that what you were asking for?
-
Did you try (full) reindexing? If it did not help, have a look at here.
-
Hello, First I recommend to use "resolution is NOT EMPTY" rather than "status in (Resolve, Closed, Done)" Anyway, you can add "resolutiondate >= 'yyyy-MM-dd' and resolutiondate <= 'yyyy-MM-dd' " to see whether the issue was fixed within sprint's interval. But you need to know sprint's date. I am not sure but, below JQL in…
-
nFeed values are wrapped with those Xml elements for standard fields because of JSD support. If you are not using this field in a Jira SD, you can try using the nFeed (deprecated) field. Here is the link for deprecated field: https://valiantys.atlassian.net/wiki/spaces/NFEED59X/pages/82773038/Deprecated+nFeed+field
-
Which plugin is this "Time in Status" gadget? That would be better to raise a support ticket in the vendor's tracking tool.
-
Is there anything on atlassian-jira.log file?
-
Have a look at this post function Assign to a user in a role, based on a field of issue post function
-
Glad to hear that
-
You're right from this point of view, and you're not alone. Here you can see similar conversation and a workaround. Thay may help. Or, could you try adding below statement after updating MutableIssue? (I am not sure, but it may work I guess) issue.store()
-
As far as I know, it is by design. You can not change updated field unless you do some hack (modifying the db value).
-
You can add anything (title, header, bullets, ..) to comment. It's free text area and all are searchable. You can search via: comment ~ 'Some string to search'
-
Try this one import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.component.ComponentAccessor def id_vaga = customFieldManager.getCustomFieldObject("customfield_16057") def key_value = issue.getCustomFieldValue(id_vaga).toString() IssueManager im =…
-
Hello, If you have the license keys, you can easily update without internet access of Jira. Just go to Manage add-ons, click on app and paste your license.
-
There is also Assets and Inventory Plugin Or you can follow this free Atlassian app for your asset management.
-
Hello, If you're writing your own plugin, it is possible. You can change scheduled task's parameters via UI. Assume you have MyScheduledTask public class MyScheduledTask implements JobRunner{ String parameter = "DEFAULT_VALUE"; public void register() { parameter = getStoredParameter(); /* do something.... */…
-
Hello Elkin, Go to Board > Configure and switch to Card layout section. Add status to the layout
-
Glad to hear that. So please accept the answer for the further usages.
-
It should definitely work. Did you return the value. It should be as below <!-- @@Formula: Object cf1Val = issue.get("customfield_11309");Object cf2Val = issue.get("customfield_11310");Object cf3Val = issue.get("customfield_11311"); Object cf4Val = issue.get("customfield_11312"); Object cf5Val =…