...
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 | ||||||
billing | billing, invoice, project, scrum, tax | ? | Might be billing accounts, invoicing etc. May need more clarification on what the existing issues in this category contain | ||||||
bitrate | bitrate,, multiplier,, units, | no | Don't think we need this as a JIRA label | ||||||
budget | budget, roles | yes | |||||||
calendar | calendar, entry calendar, week_of_year | yes | |||||||
certificate | certificate, keystore, x509 | no | Don't think we need this as a JIRA label | ||||||
configuration | configuration, multi-tenant configuration, multi-tenant, setup configuration, product configuration, find, multi-tenant, search common, configuration, multi-tenant configuration, request | yes | |||||||
contactmech | contactmech | ? | |||||||
content | content, task content,, data, demos | ? | This is a component | ||||||
common | common, configuration, multi-tenant | ? | Don't think this needs to be a standard JIRA label | ||||||
component | component, tenant component, data, tenant | ? | Does saying it is a component add value? | ||||||
consistency | consistency, create, employee, service | no | Don't think we need this as a JIRA label. What is happening is that labels are being used to capture information that would be best included in the issue summary! | ||||||
create | consistency, create, employee, service | no | Don't think we need this as a JIRA label. What is happening is that labels are being used to capture information that would be best included in the issue summary! | ||||||
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 | |||||||
currency | currency, request | 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 | ||||||
employee | consistency, create, employee, service | yes | |||||||
entity | entity | yes | |||||||
entity-auto | crud, entity-auto, shipment | no | This could fit under a generic entity label | ||||||
entry | calendar, entry | no | Don't think we need this as a JIRA label | ||||||
find | configuration, find, multi-tenant, search | no | Don't think we need this as a JIRA 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 | ||||||
invoice | invoice, roles billing, invoice, project, scrum, tax | yes | |||||||
locale | locale, theme | yes | |||||||
jar | gradle, jar | no | Too generic to have very much meaning as a JIRA label | ||||||
keystore | certificate, keystore, x509 | no | Don't think that this needs to be a JIRA label | ||||||
modalwindow | modalwindow, renderer | no | Don't think that this needs to be a JIRA label | ||||||
multiplier | bitrate,, multiplier,, units, | no | Don't think that this needs to be a JIRA label | ||||||
multi-tenant | multi-tenant configuration, multi-tenant common, configuration, multi-tenant | ? | Duplicate of tenant. Need to decide whether to use tenant or multi-tenant as the standard label | ||||||
newbie | newbie, patch | yes | we could also call it beginner... | ||||||
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... | ||||||
patch | newbie, patch | no | This doesn't need to be a label as there is a specific field for flagging patches in the issue itself | ||||||
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 | ||||||
persistence | persistence | ||||||||
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 billing, invoice, project, scrum, tax | ? | 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 | |||||||
request | configuration, request request, website currency, request | 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 invoice, roles | ? | See above | ||||||
rooms | hotel, rooms, travel | no | This would be better under travel | ||||||
scrum | billing, invoice, project, scrum, tax | ? | Does this become part of a plug-ins label | ||||||
search | configuration, find, multi-tenant, search | no | Don't think we need this as a standard JIRA label | ||||||
service | consistency, create, employee, service | no | Don't think we need this as a standard JIRA label | ||||||
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 | ||||||
svn | configuration, multi-tenant, scrum, svn | no | Don't think this needs to be a JIRA label | ||||||
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 billing, invoice, project, scrum, tax | 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 | ||||||
units | bitrate,, multiplier,, units, | no | Don't think that this needs to be a standard JIRA 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 | ||||||
widgetwebsite | request, website | yes | |||||||
week_of_year | calendar, week_of_year | no | Don't think this needs to be a JIRA label | ||||||
widget | widget field widget field, widget | yes | |||||||
x509 | certificate, keystore, x509 | ? | Does this mean anything? | ||||||
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, | request, website | ||||||||
request | |||||||||
currency, request | |||||||||
expressions | |||||||||
order, roles | |||||||||
ftl, java, links, xsd | |||||||||
address, order | |||||||||
address, order | |||||||||
campaign, roles | |||||||||
finAccount, roles | budget, roles | ||||||||
invoice, roles | |||||||||
budget, roles | |||||||||
configuration, multi-tenant, scrum, svn | |||||||||
campaign, roles | |||||||||
campaign, roles | |||||||||
budget, roles | resources, roles | ||||||||
invoice, roles | |||||||||
invoice, roles | |||||||||
PartyRelationship | |||||||||
DBMS | |||||||||
questionnaire, survey | |||||||||
content, email, quote, | |||||||||
content, quote, | |||||||||
content, quote, | |||||||||
quote | |||||||||
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 | |||||||||
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 | |||||||||
shipping | |||||||||
content, layered, quote, ux | |||||||||
entityengine | |||||||||
ecommerce, order_confirmation | |||||||||
database, readonly | |||||||||
collection, performance | |||||||||
xsd | |||||||||
...