#workflowmanagement — Public Fediverse posts

IWiG entwickelt Kalkulationssystem für Ambulantisierung
Workflow-Management soll Kliniken bei Hybrid-DRGs und AOP-Transformation unterstützen
#Ambulantisierung #AOP #HybridDRG #IWiG #Klinikmanagement #Krankenhausreform #WorkflowManagement

https://www.medconweb.de/blog/finanzierung/iwig-entwickelt-kalkulationssystem-fuer-ambulantisierung/

Improve productivity with CRM with Project Management by Commence. Manage projects, track tasks, and collaborate seamlessly while keeping customer data in one place. Streamline workflows, increase team efficiency, and deliver projects on time with an all-in-one CRM solution designed for growing businesses. https://commence.com/project-management/

#CRMProjectManagement #BusinessProductivity #WorkflowManagement #CRMSoftware #CommenceCRM

All In One Task Management in Odoo | Project, Checklist, Timesheet

Take control of your daily operations with Odoo’s powerful all-in-one task management system. From planning and assigning tasks to tracking progress and collaboration, everything is managed in one place for better efficiency and productivity.

Watch Now: https://youtu.be/zWt9tFO6o00

#Odoo #TaskManagement #OdooERP #ProjectManagement #BusinessAutomation #WorkflowManagement #Productivity #odoo18 #odoo19

🎩 Imagine Rails developers needing yet another "tree of actions" to manage their already tangled workflows 🌳. "Stepped" promises to turn their spaghetti code into... tree spaghetti 🌲🍝! With GitHub's relentless AI bells and whistles, it's like tap-dancing on quicksand while juggling chainsaws 😜🔧.
https://github.com/envirobly/stepped #RailsDevelopment #SpaghettiCode #TreeOfActions #AIIntegration #WorkflowManagement #HackerNews #ngated

🎩 Imagine Rails developers needing yet another "tree of actions" to manage their already tangled workflows 🌳. "Stepped" promises to turn their spaghetti code into... tree spaghetti 🌲🍝! With GitHub's relentless AI bells and whistles, it's like tap-dancing on quicksand while juggling chainsaws 😜🔧.
https://github.com/envirobly/stepped #RailsDevelopment #SpaghettiCode #TreeOfActions #AIIntegration #WorkflowManagement #HackerNews #ngated

🎩 Imagine Rails developers needing yet another "tree of actions" to manage their already tangled workflows 🌳. "Stepped" promises to turn their spaghetti code into... tree spaghetti 🌲🍝! With GitHub's relentless AI bells and whistles, it's like tap-dancing on quicksand while juggling chainsaws 😜🔧.
https://github.com/envirobly/stepped #RailsDevelopment #SpaghettiCode #TreeOfActions #AIIntegration #WorkflowManagement #HackerNews #ngated

🎩 Imagine Rails developers needing yet another "tree of actions" to manage their already tangled workflows 🌳. "Stepped" promises to turn their spaghetti code into... tree spaghetti 🌲🍝! With GitHub's relentless AI bells and whistles, it's like tap-dancing on quicksand while juggling chainsaws 😜🔧.
https://github.com/envirobly/stepped #RailsDevelopment #SpaghettiCode #TreeOfActions #AIIntegration #WorkflowManagement #HackerNews #ngated

This took a while. After the new version of the Snakemake paper (a rolling paper on F1000) came out, the DOI now is "working" 🥳 :

https://doi.org/10.12688/f1000research.29032.3

From my point of view, it particularly describes the working with various #HPC batch systems. And: Development did not cease. If you want to follow our announcement bot for updates: @snakemake

#Snakemake #ReproducibleComputing #DataAnalysis #OpenScience #WorkflowManagement

The Galaxy workflow management system integrates workflows and RO-Crates, enabling the export of analyses, which can be shared and restored by other users.

You can read the full paper here ▶️https://doi.org/10.1002/cctc.202401676

#PSDI #Publication #Chemistry #Workflow #WorkflowManagement #Publishing

Here’s an article I wrote a while back about using AI for curation. ChatGPT can also assist in the many functions that are required when you have multiple #Flipboard accounts. Last week in my advanced webinar I discussed simplifying workflows. If you have lots of content to add to your Flipboard accounts, setting up an AI function will make flipping easier. #ai #workflowmanagement #workflowautomation #curation #content #bloggingforbusiness #flipboardmagazines #chatgpt #openai https://about.flipboard.com/business/4-ways-i-use-ai-to-improve-content-curation-on-flipboard/

#introduction
Hello everyone! As I'm joining the #Fediverse I'd like to introduce myself.
I'm a scientist interested in #bioinformatics and #ComputationalBiology applications for #PrecisionMedicine.

In my lab, we analyze #omics data, apply #WorkflowManagement tools to run #pipelines, and explore #MixedReality for #healthcare applications.
And, obviously, we use #MachineLearning when appropriate.

Jesus, SaaS and digital tithing - Will Robbins
Contributor

Share on Twitter

Will Ro... more: http://feedproxy.google.com/~r/Techcrunch/~3/8uqr-ySJXzY/ #workflowmanagement #onlinescheduling #computerscience #contrarycapital #insightpartners #marketanalysis #freesoftware #unitedstates #extracrunch #coronavirus #glassdoor #hollywood #payments #covid-19 #religion #software #fintech #florida #netflix #column #leader #media #major #saas #tc

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten

Jira, Bugzilla, and Tales of Issue Trackers Past

It seems as though Mozilla is never not in a period of transition. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.

And if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools.

Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. I can’t code without an editor. I can’t prune without shears. They’re the part of our work that we actually touch. The code lives Out There, the garden is Outside… but the tools are in our hands.

But tools can also be group things. A shed is a tool for everyone’s tools. A workshop is a tool that others share. An Issue Tracker is a tool that helps us all coordinate work.

And group things require cooperation, agreement, and compromise.

While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira.

With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch.

In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software.

Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking?

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Apples and Oranges. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.

And that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira. Maybe they tried building workflows in Bugzilla and didn’t make it work. Maybe they were using Github Issues for a while and found it lacking. We already had multiple places to file issues, but now some of the places are Workflow Management Software.

And the rumbling has begun. And it’s no wonder, as even tools that are group things are still personal. They’re still what we touch when we craft.

The GNU-minded part of me thinks that workflow management should be built above and separate from issue tracking by the skillful use of open and performant interfaces. Bugzilla lets you query whatever you want, however you want, so why not build reporting Over There and leave me my issue tracking Here where I Like It.

The practical-minded part of me thinks that it doesn’t matter what we choose, so long as we do it deliberately and consistently.

The schedule-minded part of me notices that I should probably be filing and fixing issues rather than writing on them. And I think now’s the time to let that part win.

:chutten

Here’s an article I wrote a while back about using AI for curation. ChatGPT can also assist in the many functions that are required when you have multiple #Flipboard accounts. Last week in my advanced webinar I discussed simplifying workflows. If you have lots of content to add to your Flipboard accounts, setting up an AI function will make flipping easier. #ai #workflowmanagement #workflowautomation #curation #content #bloggingforbusiness #flipboardmagazines #chatgpt #openai https://about.flipboard.com/business/4-ways-i-use-ai-to-improve-content-curation-on-flipboard/

Here’s an article I wrote a while back about using AI for curation. ChatGPT can also assist in the many functions that are required when you have multiple #Flipboard accounts. Last week in my advanced webinar I discussed simplifying workflows. If you have lots of content to add to your Flipboard accounts, setting up an AI function will make flipping easier. #ai #workflowmanagement #workflowautomation #curation #content #bloggingforbusiness #flipboardmagazines #chatgpt #openai https://about.flipboard.com/business/4-ways-i-use-ai-to-improve-content-curation-on-flipboard/

Here’s an article I wrote a while back about using AI for curation. ChatGPT can also assist in the many functions that are required when you have multiple #Flipboard accounts. Last week in my advanced webinar I discussed simplifying workflows. If you have lots of content to add to your Flipboard accounts, setting up an AI function will make flipping easier. #ai #workflowmanagement #workflowautomation #curation #content #bloggingforbusiness #flipboardmagazines #chatgpt #openai https://about.flipboard.com/business/4-ways-i-use-ai-to-improve-content-curation-on-flipboard/

Here’s an article I wrote a while back about using AI for curation. ChatGPT can also assist in the many functions that are required when you have multiple #Flipboard accounts. Last week in my advanced webinar I discussed simplifying workflows. If you have lots of content to add to your Flipboard accounts, setting up an AI function will make flipping easier. #ai #workflowmanagement #workflowautomation #curation #content #bloggingforbusiness #flipboardmagazines #chatgpt #openai https://about.flipboard.com/business/4-ways-i-use-ai-to-improve-content-curation-on-flipboard/

Cách quản lý luồng công việc từ chat -> quyết định -> tác vụ, bạn cảm thấy như thế nào? Nhiều nhóm sử dụng sự kết hợp của Slack, Notion và Clickup nhưng cảm thấy choáng ngợp với nhiều nền tảng. Phần nào của quy trình gây khó chịu nhất? Liệu tự động hóa đơn giản có giúp việc này trở nên mượt mà hơn không? Chia sẻ ý kiến của bạn nhé!

#quảnlýcôngviệc #slack #notion #clickup #tựđộnghóacôngviệc #workflowmanagement #automation

https://www.reddit.com/r/SaaS/comments/1olguv2/feeling_overwhelmed_using_

A Sense of Doubt blog post #3612 - Crash Dive: Go Deep, Run Silent, Get it Done. https://sensedoubt.blogspot.com/2025/01/a-sense-of-doubt-blog-post-3612-crash.html #GetItDone #WorkProcess #Productivity #ExecutiveFunction #Writing #Blogging #workflowmanagement

A Sense of Doubt blog post #3612 - Crash Dive: Go Deep, Run Silent, Get it Done. https://sensedoubt.blogspot.com/2025/01/a-sense-of-doubt-blog-post-3612-crash.html #GetItDone #WorkProcess #Productivity #ExecutiveFunction #Writing #Blogging #workflowmanagement

How To Send Activity Email Notification In Odoo

Set up activity email notifications in Odoo to keep your team updated on tasks, follow-ups, and reminders. This configuration helps users receive timely email alerts for important activities and improves communication across different Odoo modules.

Watch Now: https://youtu.be/vgtZ1udMHLs

#OdooActivities #EmailNotification #OdooSetup #OdooGuide #OdooFeatures #ERP #BusinessAutomation #WorkflowManagement #DevIntelle