Details
-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.0
-
Fix Version/s: 5.7.0-b1
-
Component/s: None
-
Labels:None
Description
See subtasks for details
Admin Area
- New Quotes widget on the Client Profile page.
- Staff can create quotes, which appear almost identical to invoices.
- Staff can change the status of quotes: Draft, Accepted, Lost, Dead
- Staff can email the quote to a client (Like invoices)
- Staff can convert the quote to 1 or 2 invoices, with x% for initial invoice and remainder in the 2nd, and set the due date for each. (Or, staff can create only 1 invoice but specify the % and the % invoices is tracked with the quote so that staff can see how much the quote has been invoiced for)
- Quotes also appear under Billing > Quotes
Client Area
- New navigation link for Quotes. This could possibly be a sub-item under another link, but not sure which.
- Clients can view quotes.
- Clients can accept quotes.
– original information –
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
- Invoices generated from a quote will be separate entities, and the original quote will continue to exist.
- Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted.
- Quotes can be emailed to the client similar to invoices, one at a time or in bulk
- Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice)
- There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for
- Admins need a way to invoice for the quote: Generate a single invoice or Generate two invoices, a deposit and final amount. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice.
- Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote.
- Emailed quotes to a client should use a new email template specifically for quotes
- Should be able to set a "Valid Until" date on a quote.
- Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?)
More details needed.
1. |
Quotation System: Database |  |
Closed | Abdy Franco |
|
||||||||
2. |
Quotation System: Model | |
Closed | Abdy Franco |
|
||||||||
3. |
Quotation System: Navigation | |
Closed | Abdy Franco |
|
||||||||
4. |
Quotation System: Widgets | |
Closed | Abdy Franco |
|
||||||||
5. |
Quotation System: Add/Edit | |
Closed | Abdy Franco |
|
||||||||
6. |
Quotation System: Automation | |
Closed | Abdy Franco |
|
||||||||
7. |
Quotation System: Convert to Invoice | |
Closed | Abdy Franco |
|
||||||||
8. |
Quotation System: View/Download | |
Closed | Abdy Franco |
|
||||||||
9. |
Quotation System: Emails | |
Closed | Abdy Franco |
|
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Add a Quotation System | Quotation System |
| Rank | Ranked higher |
Paul Phillips
made changes -
| Description | This would be similar to Draft invoices, with some important distinctions. More information to come. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
1. Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
1. Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. # 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. # 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. # 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. # 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. #* 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. #* 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. #* 1. Invoices generated from a quote will be separate entities, and the original quote will continue to exist. #* 2. Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. #* Invoices generated from a quote will be separate entities, and the original quote will continue to exist. #* Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Paul Phillips
made changes -
| Description |
This would be similar to Draft invoices, with some important distinctions. More information to come.
# Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways. #* Invoices generated from a quote will be separate entities, and the original quote will continue to exist. #* Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. More details needed. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. More details needed. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. NOTE: Rather than "invoice 50% to start" etc terms, we can simplify this. When creating an invoice from a quote - just pre-fill the quote into a new invoice form. Then, it can be adjusted before its created. If you want to bill 50%, then you can adjust the amounts. You will of course have to repeat this later to bill for the final amount. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote, perhaps a partial amount (ie 50% to start, 50% upon completion) and the quote should know what invoices were generated from it and for how much. Starting with invoicing 100% to start may work for an initial release, or the option to split it into 2 invoices and just invoice both at the same time. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. NOTE: Rather than "invoice 50% to start" etc terms, we can simplify this. When creating an invoice from a quote - just pre-fill the quote into a new invoice form. Then, it can be adjusted before its created. If you want to bill 50%, then you can adjust the amounts. You will of course have to repeat this later to bill for the final amount. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes More details needed. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. More details needed. |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. # Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?) More details needed. |
Paul Phillips
made changes -
| Description |
Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways:
# Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. # Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?) More details needed. |
h2. Admin Area
* New Quotes widget on the Client Profile page. * Staff can create quotes, which appear almost identical to invoices. * Staff can change the status of quotes: Draft, Accepted, Lost, Dead * Staff can email the quote to a client (Like invoices) * Staff can convert the quote to 1 or 2 invoices, with x% for initial invoice and remainder in the 2nd, and set the due date for each. (Or, staff can create only 1 invoice but specify the % and the % invoices is tracked with the quote so that staff can see how much the quote has been invoiced for) * Quotes also appear under Billing > Quotes h2. Client Area * New navigation link for Quotes. This could possibly be a sub-item under another link, but not sure which. * Clients can view quotes. * Clients can accept quotes. -- original information -- Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways: # Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. # Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?) More details needed. |
| Fix Version/s | 5.6.0-b1 [ 11730 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Sprint | 5.6.0 Sprint 2 [ 158 ] |
| Rank | Ranked lower |
| Story Points | 13 |
| Rank | Ranked higher |
Paul Phillips
made changes -
| Sprint | 5.6.0 Sprint 3 [ 158 ] |
Paul Phillips
made changes -
| Rank | Ranked higher |
Paul Phillips
made changes -
| Fix Version/s | 5.7.0-b1 [ 11737 ] | |
| Fix Version/s | 5.6.0-b1 [ 11730 ] |
| Sprint | 5.7.0 Sprint 1 [ 169 ] |
| Rank | Ranked higher |
| Sprint | 5.7.0 Sprint 1 [ 169 ] | 5.7.0 Sprint 2 [ 171 ] |
| Rank | Ranked lower |
| Sprint | 5.7.0 Sprint 2 [ 171 ] | 5.7.0 Sprint 1 [ 169 ] |
| Rank | Ranked higher |
| Description |
h2. Admin Area
* New Quotes widget on the Client Profile page. * Staff can create quotes, which appear almost identical to invoices. * Staff can change the status of quotes: Draft, Accepted, Lost, Dead * Staff can email the quote to a client (Like invoices) * Staff can convert the quote to 1 or 2 invoices, with x% for initial invoice and remainder in the 2nd, and set the due date for each. (Or, staff can create only 1 invoice but specify the % and the % invoices is tracked with the quote so that staff can see how much the quote has been invoiced for) * Quotes also appear under Billing > Quotes h2. Client Area * New navigation link for Quotes. This could possibly be a sub-item under another link, but not sure which. * Clients can view quotes. * Clients can accept quotes. -- original information -- Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways: # Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. # Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?) More details needed. |
*_See subtasks for details_*
h2. Admin Area * New Quotes widget on the Client Profile page. * Staff can create quotes, which appear almost identical to invoices. * Staff can change the status of quotes: Draft, Accepted, Lost, Dead * Staff can email the quote to a client (Like invoices) * Staff can convert the quote to 1 or 2 invoices, with x% for initial invoice and remainder in the 2nd, and set the due date for each. (Or, staff can create only 1 invoice but specify the % and the % invoices is tracked with the quote so that staff can see how much the quote has been invoiced for) * Quotes also appear under Billing > Quotes h2. Client Area * New navigation link for Quotes. This could possibly be a sub-item under another link, but not sure which. * Clients can view quotes. * Clients can accept quotes. -- original information -- Quotations can be an invoice type like Draft if this makes sense, but will differ in several ways: # Invoices generated from a quote will be separate entities, and the original quote will continue to exist. # Quotes will have their own numbering schema and quote numbers will never be re-used, even if a quote is deleted. # Quotes can be emailed to the client similar to invoices, one at a time or in bulk # Quotes will look similar to invoices but contain different language (ie Quote instead of Invoice) # There may need to be some additional options when creating a quote like hourly rate, terms, how long the quote is good for # Admins need a way to invoice for the quote: *Generate a single invoice* or *Generate two invoices, a deposit and final amount*. If two invoices are selected, ask for % required for deposit and when the 1st and 2nd invoice should be due. We may also wish to set a billed date for the 2nd invoice as well, as it would then not be sent right away. If generating a single invoice, we should ask for the due date also for the invoice. # Clients should be able to view and approve their quotes. Approved quotes should automatically be invoiced, similar to an admin invoicing the quote. # Emailed quotes to a client should use a new email template specifically for quotes # Should be able to set a "Valid Until" date on a quote. # Add a new widget in the admin area, under a client profile page called "Quotes". If they don't want to use it, they can minimize and put at the bottom or something. For the client area, add a new nav link for Quotes (We may want it to be a sub-item of something?) More details needed. |
| Issue Type | New Feature [ 2 ] | Story [ 7 ] |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Sprint | 5.7.0 Sprint 1 [ 169 ] | 5.7.0 Sprint 1, 5.7.0 Sprint 2 [ 169, 171 ] |
| Rank | Ranked higher |
| Sprint | 5.7.0 Sprint 1, 5.7.0 Sprint 2 [ 169, 171 ] | 5.7.0 Sprint 1, 5.7.0 Sprint 2, 5.7.0 Sprint 3 [ 169, 171, 172 ] |
| Rank | Ranked higher |
| Sprint | 5.7.0 Sprint 1, 5.7.0 Sprint 2, 5.7.0 Sprint 3 [ 169, 171, 172 ] | 5.7.0 Sprint 1, 5.7.0 Sprint 2, 5.7.0 Sprint 3, 5.7.0 Sprint 4 [ 169, 171, 172, 173 ] |
| Rank | Ranked higher |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 10 minutes [ 600 ] | |
| Worklog Id | 16130 [ 16130 ] |
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Sprint | 5.7.0 Sprint 1, 5.7.0 Sprint 2, 5.7.0 Sprint 3, 5.7.0 Sprint 4 [ 169, 171, 172, 173 ] | 5.7.0 Sprint 1, 5.7.0 Sprint 2, 5.7.0 Sprint 3, 5.7.0 Sprint 4, 5.7.0 Sprint 5 [ 169, 171, 172, 173, 174 ] |
| Rank | Ranked higher |
| Time Spent | 10 minutes [ 600 ] | 5 hours, 36 minutes [ 20160 ] |
| Worklog Id | 16167 [ 16167 ] |
| Time Spent | 5 hours, 36 minutes [ 20160 ] | 1 day, 5 hours, 28 minutes [ 48480 ] |
| Worklog Id | 16178 [ 16178 ] |
| Time Spent | 1 day, 5 hours, 28 minutes [ 48480 ] | 2 days, 5 hours, 22 minutes [ 76920 ] |
| Worklog Id | 16179 [ 16179 ] |
| Time Spent | 2 days, 5 hours, 22 minutes [ 76920 ] | 3 days, 5 hours, 18 minutes [ 105480 ] |
| Worklog Id | 16180 [ 16180 ] |
| Time Spent | 3 days, 5 hours, 18 minutes [ 105480 ] | 4 days, 2 hours, 32 minutes [ 124320 ] |
| Worklog Id | 16181 [ 16181 ] |
| Status | In Review [ 5 ] | Closed [ 6 ] |