Jira API - how to ADD a custom field to an existing issue - migration

Given a project and some issues in it, I want to create a new custom field and populate it for some issues.
I see that the editmeta api returns the list of fields that are already on the issue and can be edited (updated). But how do I edit the metadata itself?
(Motivation: we migrate from another tool and want to preserve some original data after the standard export/import is done)

You will need to add new custom field(s) Jira administration. You cannot add new fields on-the-fly using common "edit issue" method.
If you are admin of whole Jira system, you can add it by yourself. If not, you will need to ask your Jira admin to do it. The new field must be also added to proper issue screens so that the field is available for editing (either from UI or from REST API).
See more here: https://confluence.atlassian.com/adminjiracloud/create-a-custom-field-991923727.html

Related

Telerik Sitefinity Add Property User

In my Sitefinity back-end there is a user section that I would like to add some setting. Something like DisplayLink where it would be a boolean value that I can set on Login of the user. Is there a way I can do that? I am using sf 14 and can't find anyway to add some setting for the user.
I believe this is what you need ...map the view externally and modify.
However keep in mind these views pull in the XHR JSON and you just expose it to the grid... Open your console and view the XHR network traffic to see the JSON object per user. There's a "Comment" field you might be able to leverage, but man the best way would be to just use a ROLE... because they can be filtered, and already come across in that JSON.
Another thing to note, is this is an OLD UI screen and likely will get revamped in the next few releases of Sitefinity rendering everything you're doing pointless... (have to re-do it with likely the new AdminApp Extensions)

Adding licence field to WSO2 API in API manager

I have the need to add a licence field to the APIs published by the API manager.
It does not seems to be any extension point beyond the api.rxt file in the resource folder.
If I modify the file and run the application the carbon app correctly show the added field, but nor the publishe nor the store are able to get the field and there is no way to get it also with REST APIs since it calls a method of a class that (in later versions) outputted fields positionally.
Is it possible to add the field, without running the risk of crashing the API Manager?
Which is the correct way?
Thanks
This change cannot be done without modifying the code. When an API is created from the Publisher app, it gets stored in the registry. The api.txt you modified, only defines the structure of this stored artifact. It may add a new field to the artifact, but to correctly populate that field, you need to modify several methods in APIProviderHostObject and APIProviderImpl + several Jaggery scripts.

ActiveCollab Project management section - adding extra custom fields while add/edit

I'm trying to develop a custom module inside ActiveCollab(4.0.11) for adding some extra fields while adding/editing projects. ActiveCollab itself has ability to add only 3 custom fields, but I need to add more fields(text,dropdown etc). I have gone through the documentation of creating modules and started working on it, but did not get much details. I have used "on_project_created" event to trigger my custom module to capture the Project form data(added the required custom fields in to ActiveCollab database tables tables and it started showing on project add/edit form automatically). Now I'm stuck with not knowing how to pass the posted values from Handler function to Controller.
Any help would be greatly appreciated.
activeCollab supports only three custom fields and there is no officially supported way to programatically add more fields. Exploiting internal API-s may work, but it is not recommended. These API-s may change or even disappear at any point, without prior notice.

Edit custom field options using API

We are trying to implement a new custom field (drop down list) which would need to be updated regularly with new options. Rather than editing the available options by hand, we were hoping to write a script which would update the custom field's options automatically by using the Rally API. Is this possible, or is it only possible to use the API to edit the records themselves?
Unfortunately it is currently not possible to manipulate custom fields through the API due to the fact that all the fields on AttributeDefinition are read-only.
I would encourage you to submit an idea for this at https://ideas.rallydev.com.

Jira SOAP API custom field

Hi I'm am trying to get the list of issues from a JIRA server using the SOAP API provided by JIRA.
I'm trying to filter the issues based on a custom field (and latter I will want to set that custom field).
If I get the list of issue it returns the custom fields for those issues along with them (I get customfieldId, key, values for each custom field) and I can get the custom field with getCustomFields methods provided by the API (to look for the ID of the field with a given name).
The issue I have is that if I login with an account that is not an admin (using the API) I can't call the getCustomFields method (it throws an exception saying I have to be an admin to do that).
My question is: Is there any other way to know which is the ID of the custom field I desire that can be done using a normal user account?
Also if you know how to set a custom field for an issue, it would also be very helpful :) (I would also like to be able to do it with a regular user account).
You have to be an admin to get a list of custom fields. Any 'normal' account can act on the custom fields via the API provided the user knows the customfield ID.
You can set the value of a custom field too, even with a 'normal' account. Again, the user needs the appropriate permissions to do this. Example provided here.
More here and here.
You can also use getFieldsForEdit(token, issueKey), which will return RemoteField[] for all fields available for edit on that issue (even if it has not yet been defined on the issue). It does not require admin permissions, but because it has the word "Edit" in the method, it does require that you have permission to edit the issue (which means, e.g., if the issue is status=Closed, it will raise an exception unless you allow editing closed issues. Unfortunately, I have yet to find a way to retrieve the RemoteField[] list (in order to map id to name), so getCustomFields() and getFieldsForEdit() appear to be the only options.
Have you tried getting a list of issues from the project, picking one, zeroing out the data, and using that as a template? That might work.
SOAP is being deprecated in favor of the REST API, which also has a better method to get this information