THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Info |
|---|
Proposal
|
NOTE: The following list of labels has been extracted from all the open OFBIz issues. This means that people have used each of these labels at least once and attached it to an OFBiz issue.is a suggested list of labels that could be used to locate specific areas within the OFBiz components. This list is significantly reduced from the existing labels for OFBiz issues.
Proposal
Clean up all existing open issues by removing any non standard labels and assign issue to the appropriate component
| Standard List | Keep - yes / no | Comments | |||
|---|---|---|---|---|---|
| accounting | no | This is already covered as a component | |||
| Accounts | no | accounting would be a better label, but it is also a component | |||
| address | no | This would fit under contactmech | |||
| AP | no | This is a component..... not sure it should be a label too | |||
| AR | no | This is a component..... not sure it should be a label too | |||
| add | no | Don't think this needs to be a JIRA label | |||
| agreements | yes | ||||
| budget | yes | ||||
| calendar | yes | This is part of the workeffort but a specific implementation of it | |||
| currency | yes | ||||
| database | yes | ||||
| dropship | agreementsyes | ||||
| ajaxfinAccount | ? | ||||
| api-change | 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 | no | This would fit under employee or project | |||
| billing | ? | Might be billing accounts, invoicing etc. May need more clarification on what the existing issues in this category contain | |||
| BillingAccountWorker | no | Don't think this needs to be the JIRA label | |||
| Birt | ? | Might be able to classify as a plug in component | |||
| bitrate | no | Don't think we need this as a JIRA label | |||
| budget | yes | ||||
| CACHE | no | Don't think this needs to be a JIRA label | |||
| calendar | yes | This is part of the workeffort but a specific implementation of it | |||
| campaign | no | Don't think we need this as a JIRA label | |||
| catalog | no | This is a component | |||
| certificate | no | Don't think we need this as a JIRA label | |||
| closure | no | Don't think we need this as a JIRA label | |||
| collection | no | Don't think we need this as a JIRA label | |||
| configuration | yes | ||||
| contactmech | ? | ||||
| content | ? | This is a component | |||
| control | no | Don't think this needs to be a standard JIRA label | |||
| common | ? | Don't think this needs to be a standard JIRA label | |||
| component | ? | Does saying it is a component add value? | |||
| consistency | 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 | 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 | no | Don't think this needs to be a JIRA label | |||
| CVE | ? | Duplicate: Is this linked to correction of security vulnerabilities? If so then security might be a better and clearer label | |||
| cve | ? | Duplicate of CVE. All others are lower case | |||
| data | yes | ||||
| currency | yes | ||||
| database | yes | ||||
| datatype | no | Think this is a bit too low level for a label. | |||
| DBMS | no | Don't think that we need this as a JIRA label | |||
| demos | no | No - this is a component | |||
| devops | ? | Don't think that we need this as a JIRA label | |||
| dropship | yes | ||||
| dynamic | no | Don't think that we need this as a JIRA label | |||
| easyfix | ? | This would fit under newbie or beginner | |||
| ecommerce | no | This is a component | |||
| EFT | no | Think this fits in payments | |||
| ? | If it is email then it could fit under contactmech If it was related to email templates then maybe a templates label..... | ||||
| employee | no | This is part of the human resources (humanres) component | |||
| employment | no | This would fit under employee | |||
| engine | no | Don't think this needls to be a JIRA labe | |||
| entity | no | This is part of the framework component | |||
| entity-auto | no | This could fit under a generic entity label | |||
| entity-condition | no | This could fit under a generic entity label | |||
| entityengine | no | This could fit under a generic entity label | |||
| entry | no | Don't think we need this as a JIRA label | |||
| ESS | no | This would fit under employee (ESS = Employee Self Service) | |||
| Expense | no | This could fit under accounting or use the accounting component | |||
| expressions | no | Don't think this needs to be a JIRA label | |||
| 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 label | |||
| finAccount | yes | Maybe write in full - financial account | |||
| find | no | Don't think we need this as a JIRA label | |||
| field | no | Having a field label doesn't give us any additional information. It is too generic | |||
| fieldtype | no | Think this is a bit too low level for a label | |||
| filter | no | Don't think that this needs to be a JIRA label | |||
| filters | no | Duplicate. Don't think this needs to be a JIRA label | |||
| focus-field-name | no | Too specific for a label | |||
| form | ? | Don't think that saying an issue is related to a form helps very much | |||
| forms | ? | One entry is form and this is forms. | |||
| ftl | yes | Or make it more obvious - and say freemarker | |||
| getBillingAccountBalance | no | Don't think that this needs to be a JIRA label | |||
| gradle | no | This is a component | |||
| groovy | yes | ||||
| GroupOrder | no | This would be better under order | |||
| hotel | no | This would be better under travel | |||
| html | ? | ||||
| humanres | no | This is a component | |||
| i18n | yes | ||||
| inline | no | Don't think this needs to be a JIRA label | |||
| invoice | yes | ||||
| layered | no | Don't think that this needs to be a JIRA label | |||
| ldap | ? | ||||
| LEAK | no | Don't think this needs to be a JIRA label | |||
| links | no | Don't think this needs to be a JIRA label | |||
| locale | yes | ||||
| lookup | no | Don't think that this needs to be a JIRA label | |||
| 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 | no | Don't think this needs to be a JIRA label | |||
| keystore | no | Don't think that this needs to be a JIRA label | |||
| management | no | Don't think that this needs to be a JIRA label | |||
| manufacturing | no | This is a component | |||
| mapping | ? | maybe | |||
| marketing | no | This is a component | |||
| MEMORY | no | Don't think that this needs to be a JIRA label | |||
| modalwindow | no | Don't think that this needs to be a JIRA label | |||
| multiplier | no | Don't think that this needs to be a JIRA label | |||
| multi-tenant | ? | Duplicate of tenant. Need to decide whether to use tenant or multi-tenant as the standard label | |||
| NetBeforeOverhead | no | Don't think this needs to be a JIRA label | |||
| NER | ? | What is this? | |||
| newbie | yes | we could also call it beginner... | |||
| NLP | ? | What is this? | |||
| ofbiz | no | We don't need ofbiz as a label | |||
| operations | ? | Not sure what this means? | |||
| order | ? | Could be purchase order, sales order... | |||
| Order | no | Duplicate | |||
| order-confirmation | no | This would fit under order | |||
| OrderPurchasePaymentSummary | no | Don't think this needs to be a JIRA label | |||
| PartyRelationship | no | This would fit under roles | |||
| patch | no | This doesn't need to be a label as there is a specific field for flagging patches in the issue itself | |||
| payment | yes | Would be better if this was called payments | |||
| payment-application | no | Think this fits in payments | |||
| payment-gateway | no | Think this fits in payments | |||
| payment-method | no | Think this fits in payments | |||
| performance | no | Duplicate. Don't think this needs to be a JIRA label | |||
| PERFORMANCE | no | Don't think this needs to be a JIRA label | |||
| persistence | no | Don't think this needs to be a JIRA label | |||
| phase | no | Don't think this needs to be a JIRA label | |||
| portal | no | Don't think this needs to be a JIRA label | |||
| portalPage | no | Don't think this needs to be a JIRA label | |||
| portlet | no | Don't think this needs to be a JIRA label | |||
| product | no | This is a component | |||
| profile | no | Don't think this needs to be a JIRA label | |||
| project | ? | If this is project manager related then I think it could be a component (even an official plug in one) | |||
| projectmgr | no | This is a component. Could use project... | |||
| purchase | ? | Not sure this is a good label, purchasing might be a better description | |||
| questionnaire | no | This is included under survey | |||
| quote | ? | ||||
| readonly | no | Don't think this needs to be a JIRA label | |||
| refactoring | yes | ||||
| registration | no | Don't think this needs to be a JIRA label | |||
| relations | ? | Unsure of what this means? Sounds like it could be more linked to roles | |||
| renderer | ? | Don't think this needs to be a JIRA label | |||
| reporting | yes | ||||
| request | no | Don't think this needs a JIRA label | |||
| request-objects | no | Don't think this needs to be a JIRA label | |||
| resources | no | Don't think this needs to be a JIRA label | |||
| role | ? | This is very generic, also there is another label roles, what the difference? or is it just duplication | |||
| roles | ? | See above | |||
| rooms | no | This would be better under travel | |||
| scrum | ? | Does this become part of a plug-ins label | |||
| search | no | Don't think we need this as a standard JIRA label | |||
| security | no | This is a component | |||
| servlet-context | no | Don't think this needs to be a JIRA label | |||
| service | no | Don't think we need this as a standard JIRA label | |||
| services | no | This is part of the framework component | |||
| session-context | no | Don't think this needs to be a JIRA label | |||
| shipment | yes | ||||
| shipping | no | This can fit under shipment | |||
| skip-start | no | Too specific to be a useful JIRA standard label | |||
| survey | yes | ||||
| Survey | no | Duplicate of survey, another example of how easy it is to create duplicates if no standard list is specified | |||
| setup | ? | Think this is too generic | |||
| svn | no | Don't think this needs to be a JIRA label | |||
| task | no | Don't think this needs to be a JIRA label | |||
| tasks | no | Duplicate. | |||
| tax | yes | ||||
| Tax | no | Duplicate that is easily created and used if we don't have a standard list | |||
| tenant | yes | Need to decide if we call it tenant or multi-tenant, we don't need both | |||
| theme | yes | ||||
| time | no | This would fit under employee or project | |||
| timesheet | no | This would fit under employee or project | |||
| tomcat | yes | ||||
| transactions | ? | This description is to generic | |||
| travel | yes | Consolidate things like hotel, rooms etc under this label | |||
| units | no | Don't think that this needs to be a standard JIRA label | |||
| upgrade | no | Don't think that this needs to be a standard JIRA label | |||
| ux | ? | ||||
| vacation | no | This would fit under employee | |||
| 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 | no | Duplicate | |||
| void | no | Don't think this needs to be a JIRA label | |||
| webapp | ? | ||||
| website | no | This is a component | |||
| webtools | ? | This is a component ... | |||
| week_of_year | no | Don't think this needs to be a JIRA label | |||
| widget | no | Don't think this needs to be a JIRA label | |||
| widgetrendering | no | This could fit under widget | |||
| x509 | ? | Does this mean anything? | |||
| yes | Maybe write in full - financial account | ||||
| ftl | yes | Or make it more obvious - and say freemarker | |||
| groovy | yes | ||||
| i18n | yes | ||||
| invoice | yes | ||||
| locale | yes | ||||
| newbie | yes | we could also call it beginner... | |||
| payment | yes | Would be better if this was called payments | |||
| refactoring | yes | ||||
| reporting | yes | ||||
| shipment | yes | ||||
| survey | yes | ||||
| tax | yes | ||||
| tenant | yes | Need to decide if we call it tenant or multi-tenant, we don't need both | |||
| tomcat | yes | ||||
| 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 | xsd | ? | Don't think this needs to be a JIRA label |
Reporter
The issue 'Reporter' is the person that creates the issue. This is automatically assigned by JIRA based on the user profile of the person creating the Jira.
...