Jira获取issue活动中改动记录，查找xx更新过xx field字段

#Jira获取issue活动中改动记录，查找xx更新过xx field字段
可以使用jira api/2/issue 接口：
Get issue GET /rest/api/2/issue/{issueIdOrKey}
jira_server_url + ‘/rest/api/2/issue/%s?expand=changelog&fields=summary’ % jira_key
fields 指定主题是因为不指定会返回所有fields字段信息！
返回值结构：
{
“changelog”:{
“total”:16,
“startAt”:0,
“histories”:Array[16],
“maxResults”:16
},
“fields”:Object{…},
“self”:“http://jira.xxxxx.com/rest/api/2/issue/xxxxxx”,
“key”:“xxxxxx”,
“id”:“xxxxx”,
“expand”:“renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations”
}

jira api/2/issue 接口：
Get issue GET /rest/api/2/issue/{issueIdOrKey}

Returns a full representation of the issue for the given issue key.

An issue JSON consists of the issue key, a collection of fields, a link to the workflow transition sub-resource, and (optionally) the HTML rendered values of any fields that support it (e.g. if wiki syntax is enabled for the description or comments).

The fields param (which can be specified multiple times) gives a comma-separated list of fields to include in the response. This can be used to retrieve a subset of fields. A particular field can be excluded by prefixing it with a minus.

By default, all (*all) fields are returned in this get-issue resource. Note: the default is different when doing a jql search – the default there is just navigable fields (*navigable).

*all - include all fields
*navigable - include just navigable fields
summary,comment - include just the summary and comments
-comment - include everything except comments (the default is *all for get-issue)
*all,-comment - include everything except comments
The {@code properties} param is similar to {@code fields} and specifies a comma-separated list of issue properties to include. Unlike {@code fields}, properties are not included by default. To include them all send {@code ?properties=*all}. You can also include only specified properties or exclude some properties with a minus (-) sign.

{@code *all} - include all properties
{@code *all, -prop1} - include all properties except {@code prop1}
{@code prop1, prop1} - include {@code prop1} and {@code prop2} properties
JIRA will attempt to identify the issue by the issueIdOrKey path parameter. This can be an issue id, or an issue key. If the issue cannot be found via an exact match, JIRA will also look for the issue in a case-insensitive way, or by looking to see if the issue was moved. In either of these cases, the request will proceed as normal (a 302 or other redirect will not be returned). The issue key contained in the response will indicate the current value of issue’s key.

The expand param is used to include, hidden by default, parts of response. This can be used to include:

renderedFields - field values in HTML format
names - display name of each field
schema - schema for each field which describes a type of the field
transitions - all possible transitions for the given issue
operations - all possibles operations which may be applied on issue
editmeta - information about how each field may be edited. It contains field’s schema as well.
changelog - history of all changes of the given issue
versionedRepresentations - REST representations of all fields. Some field may contain more recent versions. RESET representations are numbered. The greatest number always represents the most recent version. It is recommended that the most recent version is used. version for these fields which provide a more recent REST representation. After including versionedRepresentations “fields” field become hidden.
Request
QUERY PARAMETERS
parameter type description
fields string the list of fields to return for the issue. By default, all fields are returned.

expand string
properties string the list of properties to return for the issue. By default no properties are returned.

Jira获取issue活动中改动记录，查找xx更新过xx field字段相关推荐

通过Mybatis获取mysql表中重复记录的方法
输入条件:函数F返回的某表A的id列表 (id列表中的数据可能带有重复) 目标:依据该i列表 id 的顺序获取相应的记录列表. 方法:在mysql本身的语句中未发现有好的方法,即使用 in 语句也只能 ...
php获取数据库表中总记录行数并打印
<?php require("init.php");$sql = "SELECT count(*) FROM ha_user";$result = mys ...
【Android 插件化】Hook 插件化框架 ( 通过反射获取 “宿主“ 应用中的 Element[] dexElements )
Android 插件化系列文章目录 [Android 插件化]插件化简介 ( 组件化与插件化 ) [Android 插件化]插件化原理 ( JVM 内存数据 | 类加载流程 ) [Android 插件 ...
【Android 插件化】Hook 插件化框架 ( 通过反射获取 “插件包“ 中的 Element[] dexElements )
Android 插件化系列文章目录 [Android 插件化]插件化简介 ( 组件化与插件化 ) [Android 插件化]插件化原理 ( JVM 内存数据 | 类加载流程 ) [Android 插件 ...
EPICS calc模块中aCalcout记录介绍
内容 1.介绍数组计算输出或"aCalcout"记录源自sCalcout(字符串calcout)记录,sCalcout(字符串calcout)记录源自calcout记录.除了变量 ...
LinuxC下获取UDP包中的路由目的IP地址和头标识目的地址
在接受到UDP包后,有时候我们需要根据所接收到得UDP包,获取它的路由目的IP地址和头标识目的地址. (一)主要的步骤: 在setsockopt中设置IP_PKTINFO,然后通过recvmsg来获取 ...
html页面按钮删除一条数据库,需要添加一个删除按钮到一个HTML表格从数据库中删除记录与消息...
IDNameCodeActiveEdit <?php foreach($nurseries->result() as $nursery) { ?> <?php echo $nu ...
幼儿园观察记录的目的和目标_幼儿园观察记录：如何让幼儿在区角活动中真正动起来...
区角活动是幼儿园教育教学活动中的重要组成部分,它贯穿于幼儿园一日生活的各个环节当中.它是幼儿园教育中促进幼儿个性化发展的有效形式.区角活动的内容与主题结合提升目的性;区角活动的材料与本土资源结合,凸显 ...
C# API之常用操作窗口类函数详解[查找所有窗口、获取目标句柄的类名、获取窗口文本、获取当前活动窗口、通过窗口句柄获取线程ID、获取指定窗口位置]
/// <summary>/// 查找所有窗口(只要是在进程里面的)/// 如果不限制类名或者标题使用null代替/// </summary>/// <param nam ...

Jira获取issue活动中改动记录，查找xx更新过xx field字段

Jira获取issue活动中改动记录，查找xx更新过xx field字段相关推荐

最新文章

热门文章