...
Standard List | List of all currently used OFBiz JIRA labels | Keep - yes / no | Comments | |
---|---|---|---|---|
accounting | accounting, services, tax, transactions Tax,, accounting, transactions accounting, form | ? | Is this a more a component or more generic? | |
Accounts | AP, AR, Accounts | no | accounting would be a better label, but it is also a component | |
AP | AP, AR, Accounts | no | This is a component..... not sure it should be a label too | |
AR | AP, AR, Accounts | no | This is a component..... not sure it should be a label too | |
add | add, phase, project, task, void | no | Don't think this needs to be a JIRA label | |
agreements | agreement(s), dropship, purchase agreement(s), role, roles | yes | ||
ajax | ajax | ? | ||
api-change | api-change, ofbiz, tomcat | no | Don't think api-change is a label. It is more of a description of the task, we could maybe have something that is more generic e.g api | |
configuration | configuration, multi-tenant configuration, multi-tenant, setup configuration, product | yes | ||
contactmech | contactmech | ? | ||
content | content, task content,, data, demos | ? | This is a component | |
component | component, tenant component, data, tenant | ? | Does saying it is a component add value? | |
crud | crud crud, entity-auto, shipment | no | Don't think this needs to be a JIRA label | |
CVE | CVE | ? | Duplicate: Is this linked to correction of security vulnerabilities? If so then security might be a better and clearer label | |
cve | cve | ? | Duplicate of CVE. All others are lower case | |
data | component, data, tenant content,, data, demos | yes | ||
database | database, devops, refactoring | yes | ||
datatype | datatype, fieldtype | no | Think this is a bit too low level for a label. | |
demos | content,, data, demos | yes | ||
devops | database, devops, refactoring | ? | Don't think that we need this as a JIRA label | |
dropship | agreement(s), dropship, purchase | yes | ||
dynamic | dynamic, forms | |||
EFT | EFT, payment, payment-method | no | Think this fits in payments | |
entity | entity | yes | ||
entity-auto | crud, entity-auto, shipment | no | This could fit under a generic entity label | |
field | field, widget | no | Having a field label doesn't give us any additional information. It is too generic | |
fieldtype | datatype, fieldtype | no | Think this is a bit too low level for a label | |
focus-field-name | focus-field-name, skip-start | no | Too specific for a label | |
form | accounting, form | ? | Don't think that saying an issue is related to a form helps very much | |
forms | dynamic, forms | ? | One entry is form and this is forms. | |
gradle | gradle, jar | yes | ||
hotel | hotel, rooms, travel | no | This would be better under travel | |
locale | locale, theme | yes | ||
jar | gradle, jar | no | Too generic to have very much meaning as a JIRA label | |
modalwindow | modalwindow, renderer | ? | Don't think that this needs to be a JIRA label | |
multi-tenant | multi-tenant configuration, multi-tenant | ? | Duplicate of tenant. Need to decide whether to use tenant or multi-tenant as the standard label | |
ofbiz | api-change, ofbiz, tomcat | no | We don't need ofbiz as a label | |
operations | data, operations, refactoring | ? | Not sure what this means? | |
order | order, payment, payment-gateway | ? | Could be purchase order, sales order... | |
payment | payment, payment-application EFT, payment, payment-method order, payment, payment-gateway | yes | Would be better if this was called payments | |
payment-application | payment, payment-application | no | Think this fits in payments | |
payment-gateway | order, payment, payment-gateway | no | Think this fits in payments | |
payment-method | EFT, payment, payment-method | no | Think this fits in payments | |
phase | add, phase, project, task, void | no | Don't think this needs to be a JIRA label | |
product | configuration, product | yes | ||
project | is add, phase, project, task, void project, projectmgr, relations, roles | ? | If this is project manager related then I think it could be a component (even an official plug in one) | |
projectmgr | project, projectmgr, relations, roles | no | This is a component. Could use project... | |
purchase | agreement(s), dropship, purchase | ? | Not sure this is a good label, purchasing might be a better description | |
quote | agreement(s), quote | ? | ||
refactoring | refactoring refactoring, widget labels, refactoring database, devops, refactoring data, operations, refactoring | yes | ||
relations | project, projectmgr, relations, roles | ? | Unsure of what this means? Sounds like it could be more linked to roles | |
renderer | modalwindow, renderer | ? | Don't think this needs to be a JIRA label | |
reporting | reporting, vat | yes | ||
role | agreement(s), role, roles | ? | This is very generic, also there is another label roles, what the difference? or is it just duplication | |
roles | agreement(s), role, roles project, projectmgr, relations, roles | ? | See above | |
rooms | hotel, rooms, travel | no | This would be better under travel | |
services | accounting, services, tax, transactions | yes | ||
shipment | crud, entity-auto, shipment | yes | ||
skip-start | focus-field-name, skip-start skip-end, skip-start | no | Too specific to be a useful JIRA standard label | |
survey | survey | yes | ||
Survey | Survey | no | Duplicate of survey, another example of how easy it is to create duplicates if no standard list is specified | |
setup | configuration, multi-tenant, setup | ? | Think this is too generic | |
task | add, phase, project, task, void content, task | no | Don't think this needs to be a JIRA label | |
tax | accounting, services, tax, transactions tax, vat | yes | ||
Tax | Tax,, accounting, transactions | no | Duplicate that is easily created and used if we don't have a standard list | |
tenant | component, tenant component, data, tenant | yes | ||
theme | locale, theme | yes | ||
tomcat | api-change, ofbiz, tomcat | yes | ||
transactions | accounting, services, tax, transactions | ? | This description is to generic | |
travel | hotel, rooms, travel | yes | Consolidate things like hotel, rooms etc under this label | |
vat | tax, vat reporting, vat | yes | It could be under tax, but VAT does has some specific rules so separating it out from generic tax could be useful for the community | |
void | add, phase, project, task, void | no | Don't think this needs to be a JIRA label | |
widget | widget field, widget | |||
gradle, jar | ||||
newbie, patch | ||||
billing, invoice, project, scrum, tax | ||||
calendar, entry | ||||
features | ||||
GroupOrder, catalog | ||||
employment, humanres, project, projectmgr, resources | ||||
assignment, project, projectmgr, relations, roles | ||||
portal, portalPage, portlet, profile | ||||
ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | ||||
common, configuration, multi-tenant | ||||
configuration, find, multi-tenant, search | ||||
configuration, multi-tenant | ||||
configuration, request | ||||
request, website | ||||
request | ||||
currency, request | ||||
expressions | ||||
order, roles | ||||
ftl, java, links, xsd | ||||
address, order | ||||
address, order | ||||
campaign, roles | ||||
finAccount, roles | ||||
budget, roles | ||||
invoice, roles | ||||
invoice, roles | ||||
budget, roles | ||||
configuration, multi-tenant, scrum, svn | ||||
campaign, roles | ||||
campaign, roles | ||||
budget, roles | ||||
resources, roles | ||||
invoice, roles | ||||
invoice, roles | ||||
PartyRelationship | ||||
certificate, keystore, x509 | ||||
certificate, keystore, x509 | ||||
certificate, keystore, x509 | ||||
certificate, keystore, x509 | ||||
DBMS | ||||
persistence | ||||
questionnaire, survey | ||||
content, email, quote, | ||||
content, quote, | ||||
content, quote, | ||||
quote | ||||
multi-tenant | ||||
BillingAccountWorker, OrderPurchasePaymentSummary, getBillingAccountBalance | ||||
Birt, NetBeforeOverhead, Order | ||||
control, filters, request-objects, servlet-context, session-context, website | ||||
calendar, week_of_year | ||||
html, webapp, widget, widgetrendering | ||||
Expense | ||||
entity-condition, entityengine | ||||
closure, groovy, inline, patch | ||||
bitrate,, multiplier,, units, | ||||
CACHE, LEAK, MEMORY | ||||
VAT, tax | ||||
PERFORMANCE | ||||
PERFORMANCE | ||||
security | ||||
engine, entity, ldap, mapping | ||||
easyfix | ||||
content, locale, lookup | ||||
filter, phase, task | ||||
gradle, upgrade | ||||
entity, i18n, webtools | ||||
NER, NLP | ||||
consistency, create, employee, service | ||||
shipping | ||||
content, layered, quote, ux | ||||
entityengine | ||||
agreement(s), quote | ||||
ecommerce, order_confirmation | ||||
database, readonly | ||||
collection, performance | ||||
xsd | ||||
...