Transaction URL field #18

New Issue

adam · 2025-12-28T23:24:06+01:00

adam commented

2025-12-28 23:24:06 +01:00

Originally created by @DragonHeart69 on GitHub (Jan 29, 2025).

I would still like to see a URL text box in the expenses/income. Here you can then attach the link to the PDF of the invoice + the option to open it (in addition to the existing edit, duplicate & delete button ?)

Sorry for stalking, I just love your “simple” project. No commitments & no rush.

Originally created by @DragonHeart69 on GitHub (Jan 29, 2025). I would still like to see a URL text box in the expenses/income. Here you can then attach the link to the PDF of the invoice + the option to open it (in addition to the existing edit, duplicate & delete button ?) Sorry for stalking, I just love your “simple” project. No commitments & no rush.

adam added the enhancement label 2025-12-28 23:24:06 +01:00

adam closed this issue

2025-12-28 23:24:07 +01:00

adam commented

2025-12-28 23:24:07 +01:00

@eitchtee commented on GitHub (Jan 29, 2025):

Don't worry, I love the enthusiasm!

This seems like a very specific use case and at least for now, I'd rather not make the transaction form even more busy.

As a compromise, we could add limited markdown support to the notes field.

This way, you could add a note like:

[**Receipt**](https://example.com) • [Other url](https://example.com)  • [~~Yet another url~~](https://example.com) • [_Another url_](https://example.com)

or

- [**Receipt**](https://example.com)
- [Other url](https://example.com)
- [~~Yet another url~~](https://example.com)
- [_Another url_](https://example.com)

And get something like

This seems even more powerful than an URL Field as it allows for multiple urls and some custom formatting, what do you think?

@eitchtee commented on GitHub (Jan 29, 2025): Don't worry, I love the enthusiasm! This seems like a very specific use case and at least for now, I'd rather not make the transaction form even more busy. As a compromise, we could add limited markdown support to the `notes` field. This way, you could add a note like: ```markdown [**Receipt**](https://example.com) • [Other url](https://example.com) • [~~Yet another url~~](https://example.com) • [_Another url_](https://example.com) or - [**Receipt**](https://example.com) - [Other url](https://example.com) - [~~Yet another url~~](https://example.com) - [_Another url_](https://example.com) ``` And get something like ![Image](https://github.com/user-attachments/assets/e3448cf3-2cfc-4b17-9ff2-d1fb3e2e9679) This seems even more powerful than an URL Field as it allows for multiple urls and some custom formatting, what do you think?

adam commented

2025-12-28 23:24:08 +01:00

@eitchtee commented on GitHub (Jan 29, 2025):

The markdown implementation will be available on the next update.

I'm leaving this issue open so other users and you can chime in with your opinions.

@eitchtee commented on GitHub (Jan 29, 2025): The markdown implementation will be available on the next update. I'm leaving this issue open so other users and you can chime in with your opinions.

adam commented

2025-12-28 23:24:08 +01:00

@DragonHeart69 commented on GitHub (Jan 29, 2025):

thx, this is indeed a good solution. This way I can link my documents from paperless-ngx to the scheduled transactions and don't have to search manually anymore.

PS: It looks like the Readme is getting a little crowded. Maybe time to build a wiki before it gets too much ? Feel free to let me know if I can help fill it :)

@DragonHeart69 commented on GitHub (Jan 29, 2025): thx, this is indeed a good solution. This way I can link my documents from paperless-ngx to the scheduled transactions and don't have to search manually anymore. PS: It looks like the Readme is getting a little crowded. Maybe time to build a wiki before it gets too much ? Feel free to let me know if I can help fill it :)

adam commented

2025-12-28 23:24:08 +01:00

@eitchtee commented on GitHub (Jan 30, 2025):

Glad it works for you. Should be available on v0.8.3 out now.

PS: It looks like the Readme is getting a little crowded. Maybe time to build a wiki before it gets too much ? Feel free to let me know if I can help fill it :)

Any way you feel like helping would be great. I think you should have wiki editing permissions since you're a collaborator, let me know if that's not true. I definitely want to move all the technical stuff out of the readme and into the wiki, like I've done with the Import function, but if you have any other ideas for the wiki and readme feel free to add them or suggest.

A user on reddit suggested adding some basic use-cases and examples to the README.

As always, thank you @DragonHeart69

@eitchtee commented on GitHub (Jan 30, 2025): Glad it works for you. Should be available on v0.8.3 out now. > PS: It looks like the Readme is getting a little crowded. Maybe time to build a wiki before it gets too much ? Feel free to let me know if I can help fill it :) Any way you feel like helping would be great. I think you should have wiki editing permissions since you're a collaborator, let me know if that's not true. I definitely want to move all the technical stuff out of the readme and into the wiki, like I've done with the Import function, but if you have any other ideas for the wiki and readme feel free to add them or suggest. A user on reddit suggested adding some basic use-cases and examples to the README. As always, thank you @DragonHeart69

adam referenced this issue

2025-12-28 23:26:14 +01:00

[PR #18] [MERGED] feat: allow for deactivating Tags, Categories and Entities, hiding them from menus #108

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/WYGIWYH#18