FredrikOseberg
0e2c57ed87
feat: initial spike on refactoring to change
2025-10-22 13:58:16 +02:00
Fredrik Strand Oseberg
866441a1b6
feat: change request progression view ( #10835 )
2025-10-22 12:27:24 +02:00
Thomas Heartman
b9d81e5f59
chore: align text to cell top ( #10837 )
...
First part of UI refactoring for the change requests table: align
content to the top of the cell to facilitate scanning the table.
To facilitate this, I've mad the paginated table stylable by adding a
class name.
Before:
<img width="1810" height="1500" alt="image"
src="https://github.com/user-attachments/assets/febc9471-5d57-4afa-a9b0-0d22044fcd92 "
/>
After:
<img width="1809" height="1326" alt="image"
src="https://github.com/user-attachments/assets/e6aea2e9-0f1d-42f9-bd09-ad7317acbd4e "
/>
2025-10-21 14:08:03 +02:00
Nuno Góis
1b60ed5df8
chore: show edge instances in license info ( #10810 )
...
https://linear.app/unleash/issue/2-3981/show-edge-instances-in-license-information-in-unleash
Show edge instances in license info.
Adapts to new logic, so resources are only shown if they are present.
2025-10-20 14:49:41 +01:00
Mateusz Kwasniewski
f37fde2a27
feat: release plan cr conflict ( #10831 )
2025-10-20 15:39:06 +02:00
Thomas Heartman
ca4ec203c6
feat: display median calculation ( #10763 )
...
Adds the median calculation to the new flags in production widget and
allows the median to take batched data into account:
<img width="1288" height="530" alt="image"
src="https://github.com/user-attachments/assets/5052dad1-03fa-4ce6-8626-ff4f6a5d818f "
/>
To achieve this, it was necessary to extract the data aggregation method
from the NewProductionFlagsChart component, so that we could use the
data (to calculate the median) at a higher level in the tree. Because
the data is now passed around outside of the chart component, I've also
updated the `ChartDataResult` type to a proper union type that contains
the state and the data.
2025-10-20 11:49:42 +00:00
Thomas Heartman
b18b128e52
feat: add median per week calculation for the new flags in production widget ( #10829 )
2025-10-20 12:17:18 +02:00
Mateusz Kwasniewski
0fda3e7cf1
feat: delete milestone progression with CR ( #10828 )
2025-10-17 14:49:03 +02:00
Jaanus Sellin
c8ca11aebb
feat: add billing invoices skeletons ( #10827 )
...
Since we load directly from Stripe, it takes a little time. Good to have
skeletons.
<img width="2151" height="1587" alt="Screenshot from 2025-10-17
15-32-10"
src="https://github.com/user-attachments/assets/be767ea1-b95f-4ef3-abf6-e8302e7092fd "
/>
2025-10-17 15:40:36 +03:00
Jaanus Sellin
faad097915
feat: overages should be rouned down to nearest integer ( #10826 )
2025-10-17 15:09:52 +03:00
Jaanus Sellin
adb1d200ea
feat: only show detailed billing for consumption and payg ( #10825 )
2025-10-17 14:11:19 +03:00
Jaanus Sellin
3f9a726db6
refactor: move invoice logic into separate file/function ( #10824 )
...
Extract calculateEstimateTotals and some utility functions.
2025-10-17 14:11:14 +03:00
Jaanus Sellin
aec793ddc7
feat: calculate the esimtate invoice numbers ( #10823 )
2025-10-17 13:24:09 +03:00
Gastón Fournier
91ecf2fabd
chore: remove uuid from the frontend ( #10808 )
...
Frontend only of: https://github.com/Unleash/unleash/pull/10806
## About the changes
This PR drops the uuid package from node modules and replaces it with
standard randomUUID usage that is available from 14.17 onwards, and we
have a minimum requirement of node 20 at Unleash.
[Node.js
crypto](https://nodejs.org/api/crypto.html#cryptorandomuuidoptions )
[Web
crypto](https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID )
Co-authored-by: Anastasiia Hladina <anastasiia.hladina@gmail.com>
2025-10-17 10:31:48 +02:00
Jaanus Sellin
e9d2b30603
feat: add taxes to invoices ( #10821 )
2025-10-17 09:49:09 +03:00
Fredrik Strand Oseberg
795b674133
feat: add change request support for updating milestone progressions ( #10819 )
2025-10-16 16:52:02 +02:00
Jaanus Sellin
022226dd43
chore: generate orval ( #10820 )
2025-10-16 16:11:39 +03:00
Tymoteusz Czech
b81691b89e
feat: invoices ui improvements ( #10813 )
2025-10-16 12:30:01 +00:00
Fredrik Strand Oseberg
045ef5a20e
refactor: consolidate release plan change request dialogs ( #10817 )
2025-10-16 13:55:52 +02:00
Thomas Heartman
9096340afb
refactor: split the stat card widget into its own component ( #10815 )
...
Prepares it for being shared between the new flags in production and the
archived to created ration sections.
The card in question is this one:
<img width="310" height="177" alt="image"
src="https://github.com/user-attachments/assets/66549601-36cd-4ccc-b175-79bd049ed1d4 "
/>
2025-10-16 13:53:32 +02:00
Fredrik Strand Oseberg
154dc6f5eb
feat: add change request support for milestone progressions ( #10814 )
2025-10-16 11:57:28 +02:00
Thomas Heartman
2cc1bf978b
chore: add todo note with flag to remember a refactor ( #10811 )
...
So that we remember to revisit this line when we remove the flag.
2025-10-16 09:53:58 +02:00
Thomas Heartman
07c947949e
fix: populate all weeks in charts ( #10800 )
...
When selecting a date range, the chart now shows you the entire range,
even if there's only data for parts of it.
This ensures that both the new flags in production chart and the created
vs archived chart show the same period and not two different ones (other
charts can be updated later).
Before:
<img width="2356" height="1536" alt="image"
src="https://github.com/user-attachments/assets/11912a2f-7a68-4405-acfa-d98d0eb69cf8 "
/>
After:
<img width="1294" height="963" alt="image"
src="https://github.com/user-attachments/assets/e932665c-9f7c-4b4e-9e14-34a1e6e71a69 "
/>
It also ensures that the 4 week batching works the same for both charts.
For line charts, only the dates with data will be rendered as a line.
For the bar chart, dates without data can still be hovered and show
empty (zero) data.
<img width="1341" height="447" alt="image"
src="https://github.com/user-attachments/assets/531266ca-02e3-4402-9b29-ce4259274e0c "
/>
<img width="1304" height="448" alt="image"
src="https://github.com/user-attachments/assets/42a0bbe9-c701-4f3f-8b10-9ef7017a9b9f "
/>
Also prevents us from showing the wrong period if there is no data for
the selected project
Before:
<img width="1292" height="960" alt="image"
src="https://github.com/user-attachments/assets/6d61a653-7bee-43d9-9c25-5d5bdb29a803 "
/>
After:
<img width="1295" height="507" alt="image"
src="https://github.com/user-attachments/assets/91994094-cd0d-495e-a41f-f92b6b7d72c9 "
/>
Finally, it happily graphs multiple projects at their individual data
points in time:
<img width="1314" height="537" alt="image"
src="https://github.com/user-attachments/assets/d382d919-fda4-4c35-8d8e-2e66dd3bed66 "
/>
2025-10-16 09:52:33 +02:00
Nuno Góis
4ff41fa6a9
chore: add warning about release plans in import-export ( #10805 )
...
https://linear.app/unleash/issue/2-3965/add-a-note-if-were-exporting-that-we-dont-understand-release-plans-in
Adds a warning about release plans in import/export.
It's not trivial to know every flag that will be exported in every
scenario, and whether they have release plans, so our logic here is
"have you configured release templates?"
<img width="706" height="516" alt="image"
src="https://github.com/user-attachments/assets/68ba8618-9887-491c-b46e-256b45700d74 "
/>
<img width="732" height="503" alt="image"
src="https://github.com/user-attachments/assets/086e37d4-78ae-4647-93a2-5d1845c2758a "
/>
2025-10-15 14:44:30 +01:00
Nuno Góis
f3ab70aeca
chore: add alert about release plans when cloning flag ( #10802 )
...
https://linear.app/unleash/issue/2-3966/cloning-a-feature-will-not-clone-release-plans
Adds an alert when cloning a feature flag with a release plan.
Requires the `featureReleasePlans` feature flag.
<img width="1162" height="568" alt="image"
src="https://github.com/user-attachments/assets/325db586-14b9-4ce4-9d7c-6f680017c6ac "
/>
2025-10-15 14:17:34 +01:00
Mateusz Kwasniewski
10c30751d3
feat: improve permission messaging ( #10804 )
2025-10-15 14:33:53 +02:00
Jaanus Sellin
e83d92975c
fix: now showing either payg or consumption ( #10803 )
...
1. Make it show either payg or consumption.
2. Add paid tag.
2025-10-15 10:32:51 +00:00
Jaanus Sellin
bffec9bc4d
feat: align billing page design with figma ( #10801 )
...
1. Splitting main row and usage row, as they have so much different
logic already now.
2. Main lines, keep only included, remove quantity
3. Add correct headers for usage lines
4. Add current consumption also as number
Old design
<img width="1502" height="906" alt="image"
src="https://github.com/user-attachments/assets/ab4fdca9-1a04-4381-88a6-9ce643f71d78 "
/>
New design
<img width="1502" height="906" alt="Screenshot from 2025-10-15 10-36-16"
src="https://github.com/user-attachments/assets/2607a91d-22de-4f72-9e59-d2212b1f5888 "
/>
2025-10-15 08:28:51 +00:00
Nuno Góis
715119741b
fix: hide enable strategy dialog when there are release plans ( #10796 )
...
https://linear.app/unleash/issue/2-3953/fix-enable-environment-modal-when-there-are-release-plans
Prevents the "environment needs at least one enabled strategy" dialog
from showing up if you have added a release plan.
This relies on the new `featureReleasePlans` feature flag.
PS: Maybe we should revisit this dialog in the future. We don't usually
see it, and maybe it should trigger the new "add strategy" modal?
<img width="684" height="399" alt="image"
src="https://github.com/user-attachments/assets/2f8213db-22b4-4618-b8e2-15eca096d465 "
/>
2025-10-15 09:21:23 +01:00
Tymoteusz Czech
38bb9b3bfc
feat: enhance billing invoice components ( #10799 )
...
## About the changes
- Hide "included usage" column if an invoice doesn't have any items that
have lines with `limit`
- Minor component types refactors
- Only open (extend accordion) for the first invoice on the list
2025-10-15 10:00:59 +03:00
Mateusz Kwasniewski
61a82673e9
feat: changing milestone progression url ( #10795 )
2025-10-14 15:57:28 +02:00
Tymoteusz Czech
b5d1f6e075
chore: remove legacy flag UI ( #10781 )
2025-10-14 11:00:51 +02:00
Tymoteusz Czech
7efd707dee
Fix: invoice page debugging ( #10791 )
2025-10-14 08:01:38 +00:00
Fredrik Strand Oseberg
bc740bbe2f
feat: add milestone progression UI with projected start times ( #10790 )
2025-10-13 17:02:30 +02:00
David Leek
e890968048
feat: apply strategy suggestion directly when clicked ( #10779 )
2025-10-13 12:20:49 +02:00
Fredrik Strand Oseberg
0edbc7d595
feat: add inline editing for milestone progressions ( #10777 )
2025-10-13 11:53:45 +02:00
Jaanus Sellin
0d252558c4
feat: add new dates and plan price ( #10774 )
...
<img width="2159" height="1617" alt="image"
src="https://github.com/user-attachments/assets/478ea289-dc0f-439e-92e4-a22fa44a0650 "
/>
2025-10-10 13:44:58 +03:00
Fredrik Strand Oseberg
4500f484ec
feat: improve milestone visual states in release plans ( #10775 )
2025-10-10 12:34:20 +02:00
Fredrik Strand Oseberg
ce2ef4fe6f
feat: add delete functionality for milestone progressions ( #10770 )
2025-10-10 09:10:10 +02:00
Jaanus Sellin
938d25828f
chore: update orval types ( #10769 )
2025-10-09 21:15:39 +03:00
Fredrik Strand Oseberg
a922801690
feat: Add transition condition UI for release plan milestones ( #10768 )
2025-10-09 11:41:58 +02:00
Fredrik Strand Oseberg
386c7d5bc6
chore: get release plans from features endpoint ( #10764 )
2025-10-09 10:12:56 +02:00
Thomas Heartman
7044cd4b1a
feat: Add batching functionality to new flags in production ( #10756 )
...
Adds the same batching functionality that was added to the
archived:created chart to the new flags in production chart.
In doing so, I've extracted the batching algorithm and the batched
tooltip title creation, as well as the ChartDataResult type (though
naming suggestions are still welcome on that front).
Locale 'ja':
<img width="1143" height="370" alt="image"
src="https://github.com/user-attachments/assets/827b41c6-0e67-46f4-8f82-4ba12e2120bb "
/>
Locale 'no':
<img width="1475" height="554" alt="image"
src="https://github.com/user-attachments/assets/6125c318-25fb-42bd-a520-44e6a7f7ece7 "
/>
2025-10-08 12:40:11 +00:00
Mateusz Kwasniewski
cf018020df
chore: feature release plans flag ( #10762 )
2025-10-08 14:19:22 +02:00
Tymoteusz Czech
4ed138c151
Billing info updates ( #10761 )
2025-10-08 12:11:24 +00:00
Fredrik Strand Oseberg
1d4f72cf81
feat: improve milestone automation UI positioning and styling ( #10758 )
2025-10-08 11:56:41 +02:00
Fredrik Strand Oseberg
8072bc6706
feat: implement milestone progression form ( #10749 )
2025-10-08 10:15:08 +02:00
Tymoteusz Czech
183d436e59
feat: invoice sections ( #10744 )
...
Currency formatting and cleaner invoice components
2025-10-08 09:15:43 +02:00
Thomas Heartman
3e10ca6611
fix: highlight is too wide when batching weeks in archived:created chart ( #10751 )
...
Makes it so that the default width calculation for the highlighter
plugin attempts to first use the number of entries in the data set for
the x axis, but falls back to using the number of categories if that is
not available. This is probably the more "correct" / "do what I mean"
approach to setting highlighter width.
Fixes an issue where the highlight would be too wide if the labels were
set to "auto" instead of "data".
The width function is only used in two places (the archived:created
graph and the network graph). Both of those work fine with the new
update.
Before:
<img width="831" height="401" alt="image"
src="https://github.com/user-attachments/assets/8487b95f-cc49-4ff6-a519-7f79e1048eed "
/>
After:
<img width="886" height="378" alt="image"
src="https://github.com/user-attachments/assets/ad2102cb-3342-4a28-aa54-6b31caa495e1 "
/>
2025-10-07 14:34:06 +02:00
Thomas Heartman
28d7672a58
feat: batch week data if the shown time span is greater than 12 weeks. ( #10745 )
...
Implements batching of data points in the archived:created chart: when
there's 12 or more weeks of data, batch data into batches of 4 weeks at
a time. When we batch data, we also switch the labeling to be
month-based and auto-generated (cf the inline comment with more
details).
<img width="798" height="317" alt="image"
src="https://github.com/user-attachments/assets/068ee528-a6d6-4aaf-ac81-c729c2c813d1 "
/>
The current implementation batches into groups of 4 weeks, but this can
easily be parameterized to support arbitrary batch sizes.
Because of the batching, we also now need to adjust the tooltip title in
those cases. This is handled by a callback.
2025-10-07 13:51:45 +02:00
