I don't quite understand what is meant by this ticket. Need to ask client.
From meeting notes:
We need to have other information than just the name, it's not only us that has a request, but also retailers that can ask us to send things. A combination of a sales-point and an exhibition place. Sometimes things are only in one place for a limited time, like 3 months. Also, we need to add ways to keep our flights private or announce them as public. With arrangements outside of this CMS, you need ways to announce these and ask others to contribute to feral trade.
Since the backend is just used for data-entry, I'm not sure where these flights would be announced. Perhaps in a selectable dropdown in the dispatches item?
I don't quite understand what is meant by this ticket. Need to ask client.
From meeting notes:
> We need to have other information than just the name, it's not only us that has a request, but also retailers that can ask us to send things. A combination of a sales-point and an exhibition place. Sometimes things are only in one place for a limited time, like 3 months. Also, we need to add ways to keep our flights private or announce them as public. With arrangements outside of this CMS, you need ways to announce these and ask others to contribute to feral trade.
Since the backend is just used for data-entry, I'm not sure where these flights would be announced. Perhaps in a selectable dropdown in the dispatches item?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I don't quite understand what is meant by this ticket. Need to ask client.
From meeting notes:
Since the backend is just used for data-entry, I'm not sure where these flights would be announced. Perhaps in a selectable dropdown in the dispatches item?