...
Info |
---|
Proposal
|
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 componentaddress | |||
address, order | no | This would fit under contactmech | ||||
AP | AP, AR, Accounts | no | This is a component..... not sure it should be a label tooAR | |||
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 | 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 | |||
assignement | assignment, project, projectmgr, relations, roles | no | This would fit under employee or project | |||
billing | billing, invoice, project, scrum, tax | ? | ? | Might be billing accounts, invoicing etc. May need more clarification on what the existing issues in this category containBillingAccountWorker | ||
BillingAccountWorker, OrderPurchasePaymentSummary, getBillingAccountBalance | no | Don't think this needs to be the JIRA label | ||||
Birt | Birt, NetBeforeOverhead, Order | ? | Might be able to classify as a plug in component | |||
bitrate | bitrate,, multiplier,, units, | no | Don't think we need this as a JIRA labelbudget | |||
budget, roles | yes | |||||
CACHE | CACHE, LEAK, MEMORY | no | Don't think this needs to be a JIRA labelcalendar | |||
calendar, entry calendar, week_of_year | yes | |||||
campaign | campaign, roles | no | Don't think we need this as a JIRA labelcatalog | |||
GroupOrder, catalog | no | This is a component | ||||
certificate | certificate, keystore, x509 | no | Don't think we need this as a JIRA labelclosure | |||
closure, groovy, inline, patch | no | Don't think we need this as a JIRA label | ||||
collection | collection, performance | 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 | ? | ||||
yes | ||||||
contactmech | ? | |||||
content | content | content, task content,, data, demos content, email, quote, | ? | This is a component | ||
control | control, filters, request-objects, servlet-context, session-context, website | no | Don't think this needs to be a standard JIRA labelcommon | |||
common, configuration, multi-tenant | ? | Don't think this needs to be a standard JIRA labelcomponent | ||||
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 labelCVE | |||
CVE | ? | Duplicate: Is this linked to correction of security vulnerabilities? If so then security might be a better and clearer labelcve | ||||
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 database, readonly | yes | datatype | |||
datatype, fieldtype | no | Think this is a bit too low level for a label.DBMS | ||||
DBMS | no | Don't think that we need this as a JIRA 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 | no | Don't think that we need this as a JIRA labeleasyfix | ||||
easyfix | ? | This would fit under newbie or beginnerecommerce | ||||
ecommerce, order_confirmation | yes | |||||
EFT | EFT, payment, payment-method | no | Think this fits in payments | |||
content, email, quote, | ? | If it is email then it could fit under contactmech If it was related to email templates then maybe a templates label..... | ||||
employee | consistency, create, employee, service ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | yes | yes | |||
employment | employment | employment, humanres, project, projectmgr, resources | no | This would fit under employeeengine | ||
engine, entity, ldap, mapping | no | Don't think this needls to be a JIRA labe | ||||
entity | entity entity, i18n, webtools engine, entity, ldap, mapping | yes | entity-auto | |||
crud, entity-auto, shipment | no | This could fit under a generic entity labelentity-condition | ||||
entity-condition, entityengine | no | This could fit under a generic entity label | ||||
entityengine | entity-condition, entityengine | no | This could fit under a generic entity labelentry | |||
calendar, entry | no | Don't think we need this as a JIRA label | ||||
ESS | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | no | This would fit under employee (ESS = This would fit under employee (ESS = Employee Self Service)Expense | ||
Expense | no | This could fit under accounting or use the accounting component | ||||
expressions | expressions | no | Don't think this needs to be a JIRA label | |||
features | features | no | There is an issue type 'New Feature' so this does not have to be a label. If it is product features then it needs to be a under the product labelfinAccount | |||
finAccount, roles | yes | |||||
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 | |||
filter | filter, phase, task | no | Don't think that this needs to be a JIRA label | |||
filterscontrol, filters, request-objects, servlet-context, session-context, website | no | Duplicate. Don't think this needs to be a JIRA label | ||||
focus-field-name | focus-field-name, skip-start | no | Too specific for a labelform | |||
accounting, form | ? | Don't think that saying an issue is related to a form helps very muchforms | ||||
dynamic, forms | ? | One entry is form and this is forms. | ||||
ftl | ftl, java, links, xsd | yes | yes | Or make it more obvious - and say freemarkergetBillingAccountBalance | ||
BillingAccountWorker, OrderPurchasePaymentSummary, getBillingAccountBalance | no | Don't think that this needs to be a JIRA label | ||||
gradle | gradle, jar | yes | ||||
groovy | closure, groovy, inline, patch | yes | ||||
GroupOrder | GroupOrder, catalog | no | This would be better under order | |||
hotel | hotel, rooms, travel | no | This would be better under travel | |||
html | html, webapp, widget, widgetrendering | ? | ||||
humanres | employment, humanres, project, projectmgr, resources | no | This is a component | |||
i18n | entity, i18n, webtools | yes | ||||
inline | closure, groovy, inline, patch | no | Don't think this needs to be a JIRA label | invoice | invoice, roles | |
billing, invoice, project, scrum, tax | yes | |||||
layered | content, layered, quote, ux | no | Don't think that this needs to be a JIRA labelldap | |||
engine, entity, ldap, mapping | ? | |||||
LEAK | CACHE, LEAK, MEMORY | no | no | Don't think this needs to be a JIRA label | ||
linksftl, java, links, xsd | no | Don't think this needs to be a JIRA label | ||||
locale | locale, theme | yes | ||||
lookup | content, locale, lookup | no | Don't think that this needs to be a JIRA label | |||
jar | gradle, jar | no | Don't think that this needs to be a JIRA label. Too generic to have very much meaning as a JIRA label | |||
java | ftl, java, links, xsd | no | Don't think this needs to be a JIRA label | |||
keystore | certificate, keystore, x509 | no | Don't think that this needs to be a JIRA label | |||
management | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | Don't think that this needs to be a JIRA label | |||
manufacturingESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | This is a component | ||||
mapping | engine, entity, ldap, mapping | ? | maybe | |||
marketing | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | no | This is This is a component | ||
MEMORY | CACHE, LEAK, MEMORY | 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 labelmulti-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 | ||||
NetBeforeOverhead | Birt, NetBeforeOverhead, Order | no | Don't think this needs to be a JIRA labelNER | |||
NER, NLP | ? | What is this?newbie | ||||
newbie, patch | yes | we could also call it beginner...NLP | ||||
NER, NLP | ? | What is this? | ||||
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 order, roles | ? | Could be purchase order, sales orderCould be purchase order, sales order... | ||
Order | Birt, NetBeforeOverhead, Order | no | Duplicate | |||
order-confirmation | ecommerce, order_confirmation | no | This would fit under order | |||
OrderPurchasePaymentSummary | BillingAccountWorker, , getBillingAccountBalance | no | Don't think this needs to be a JIRA labelPartyRelationship | |||
PartyRelationship | no | This would fit under roles | ||||
patch | newbie, patch | no | This doesn't need to be a label as there is a specific field for flagging patches in the issue itselfpayment | |||
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 paymentspayment-gateway | |||
order, payment, payment-gateway | no | Think this fits in payments | ||||
payment-method | EFT, payment, payment-method | no | Think this fits in paymentsperformance | |||
collection, performance | no | Duplicate. Don't think this needs to be a JIRA label | ||||
PERFORMANCE | PERFORMANCE | no | Don't think this needs to be a JIRA labelpersistence | |||
persistence | no | Don't think this needs to be a JIRA label | ||||
phase | add, phase, project, task, void | no | no | Don't Don't think this needs to be a JIRA labelportal | ||
portal, portalPage, portlet, profile | no | Don't think this needs to be a JIRA label | ||||
portalPage | portal, portalPage, portlet, profile | no | Don't think this needs to be a JIRA label | |||
portlet | portal, portalPage, portlet, profile | no | Don't think this needs to be a JIRA labelproduct | |||
configuration, product | yes | |||||
profile | portal, portalPage, portlet, profile | no | Don't think this needs to be a JIRA label | |||
project | is add, phase, project, task, void project, projectmgr, relations, roles billing, invoice, project, scrum, tax employment, humanres, project, projectmgr, resources assignment, 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 employment, humanres, project, projectmgr, resources assignment, project, projectmgr, relations, roles | no | no | This 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 | |||
questionnaire | questionnaire, survey | no | This is included under surveyquote | |||
agreement(s), quote | ? | |||||
readonly | database, readonly | no | Don't think this needs to be a JIRA labelrefactoring | |||
refactoring refactoring, widget labels, refactoring database, devops, refactoring data, operations, refactoring | yes | registration | ||||
ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | Don't think this needs to be a JIRA label | ||||
relations | project, projectmgr, relations, roles assignment, 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 labelreporting | |||
reporting, vat | yes | |||||
request | configuration, request request, website currency, request | yes | ||||
request-objects | control, filters, request-objects, servlet-context, session-context, website | no | Don't think this needs to be a JIRA label | |||
resources | resources, roles employment, humanres, project, projectmgr, resources | no | Don't think this needs to be a JIRA labelrole | |||
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 assignment, project, projectmgr, relations, roles | ? | See above | ? | See above | |
rooms | 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 labelsecurity | |||
security | yes | |||||
servlet-context | control, filters, request-objects, servlet-context, session-context, website | no | Don't think this needs to be a JIRA label | |||
service | consistency, create, employee, service | no | Don't think we need this as a standard JIRA labelservices | |||
accounting, services, tax, transactions | yes | |||||
session-context | control, filters, request-objects, servlet-context, session-context, website | no | Don't think this needs to be a JIRA label | |||
shipment | crud, entity-auto, shipment | yes | yes | |||
shipping | shipping | no | This can fit under shipment | skip-start | focus-field-name, skip-start | |
skip-end, skip-start | no | Too specific to be a useful JIRA standard label | ||||
survey | survey questionnaire, 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 | |||
tasks | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | Duplicate. | 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 | yes | |||
time | time | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | This would fit under employee or project | ||
timesheet | ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | This would fit under employee or project | |||
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 | |||
upgrade | gradle, upgrade | no | Don't think that this needs to be a standard JIRA labelux | |||
content, layered, quote, ux | ? | vacation | ||||
ESS, employee, management, manufacturing, marketing, registration,, tasks, time, timesheet, vacation, | no | This would fit under employeeemployee | ||||
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 | |||
VAT | VAT, tax | no | Duplicatevoid | |||
add, phase, project, task, void | no | Don't think this needs to be a JIRA label | ||||
webapp | html, webapp, widget, widgetrendering | ? | ||||
website | request, website control, filters, request-objects, servlet-context, session-context, website | yes | ||||
webtools | entity, i18n, webtools | ? | This is a component ... | |||
week_of_year | calendar, week_of_year | no | Don't think this needs to be a JIRA label | |||
widget widget field, widget html, webapp, widget, widgetrendering | yes | |||||
widgetrendering | html, webapp, widget, widgetrendering | no | This could fit under widget | |||
x509 | certificate, keystore, x509 | ? | Does this mean anything? | xsd | xsdftl, java, links, | |
xsd | ? | Don't think this needs to be a JIRA label |
...