Termp update and bug fix

@Microlent

Hello, I am Dr. Rajesh Rolen, PhD in Computer Science & Engineering, with experience of over 20+ years in Software Development, JavaScript, Software Testing, Development, Software Architecture As a preferred freelancer in the top 1%, I have done 400+ projects here on freelancer.com, I have 4.9 ratings out of 5 on average, which showcases my quality of work and timely delivery. Key Highlights: - Free Hosting Support on the Cloud or any desired platform. - Free 3 months of post-delivery support to ensure that our client doesn’t face any challenges after the launch of the project. - Free Dedicated tester on projects to ensure quality delivery, so clients don’t need to act as a tester. - 10+ Years experience UI/UX team to ensure intuitive UI. Portfolio: https://www.freelancer.com/u/Microlent Please open the chat and send me a message, so we can have a more detailed discussion about the project to give you the project timeline and cost. Thank you for considering my services. I look forward to engaging in a productive conversation and understanding how I can be of assistance in bringing your project to life. Regards Rajesh Rolen

@ukroficer

Hello, I would treat this as a structured bug-fix pass on your live development environment, not isolated tickets, because the 58 open items cut across permissions, DOCX/PDF handling, workflow state, billing, and UI behavior. With your GitHub branch + PR process and Trello details, the right approach is to group issues by subsystem first so fixes do not conflict or reopen related bugs. - I will triage the 58 items into modules and define a safe fix order. - I will handle each assigned issue on a branch with clear PR notes and test steps. - I will deploy branch updates to the dev server for your live validation. - I will propose regression checks for permissions, workflow, exports, and subscriptions. The main scope question is: what stack is the current app built on, and are billing and document export handled in-house or through external services? I can start with the CSV and Trello review and return a fix sequence first. Roman

@AwaisChaudhry

Hello, Your 58-item development backlog is a substantial QA and delivery effort, and I can help turn the Trello issues into controlled, testable releases. I’ll review the CSV and issue details, reproduce each defect, trace root causes across document workflows, permissions, billing, analytics, translation features, and UI behavior, then implement focused updates through your GitHub branch and Pull Request workflow. I’ll apply Software Architecture judgment to avoid regressions, use JavaScript and Java where appropriate, and validate fixes with structured Software Testing before deploying the branch to your development server. Each change can be mapped back to its Trello item, with clear testing notes and follow-up fixes based on your team’s findings. Project Management will remain visible through prioritization, progress tracking, and concise status updates across the 58 issues. Which issue group is the highest priority for your next development release, and how should completion be measured? I’m ready to begin by reviewing the CSV, Trello workflow, repository structure, and highest-priority blockers. Best regards, Muhammad Awais

@hirujiyu

Hi there, Yes, I can take ownership of the 58 open issues and work through them systematically in your existing development environment. I’m comfortable joining an existing codebase, understanding the current workflows, fixing bugs and delivering changes through a proper GitHub branch → PR → development deployment → testing cycle. Here's what I will deliver :- ✔️ PDF/DOCX upload, viewer & export issues ✔️ Roles, permissions & workflow fixes ✔️ Translation workspace, Term Base & Translation Memory ✔️ Analytics, project completion & activity fixes ✔️ Billing, trials & subscription issues ✔️ Organization/session and UI improvements ✔️ Regression testing and PR-based delivery I’ll review the Trello details and CSV issue list first, group items by priority/dependency, then work through them with proper testing and documentation. I’m available to start immediately and can provide a realistic estimate after reviewing the issue list and codebase. Thank you.

@starttechno

I would begin by reproducing the 403 on the Project Manager `Pre-Translate` request and the `Cannot Advance Workflow` error in both Simple Translation and Single Review workflows, then trace each issue from the Trello reproduction steps through the API and UI. I’ll work through the 58 CSV/Trello items in priority order, focusing on shared permission, workflow, Stripe billing, PDF/DOCX conversion, analytics, and workspace logic rather than applying isolated patches. Each change will be committed on a GitHub branch, submitted through a Pull Request, deployed to development, and adjusted from your testing feedback. The completed fixes and feature updates will be delivered on the development server within 7 days. Should the failed-payment items follow Stripe’s existing subscription update flow exactly? Muhammad Saad

@seefattechnologi

Exactly----->>CHECKED attachemnst------------- I will Complete this project as per the given scope of work ----Termp update and bug fix You will get clear communication, creative thinking, and reliable delivery without constant follow-ups. I am Passionate PHP /Full stack developer having rich experience with so many successful Tasks. Please ping me to get started and provide you great results. Thanks

@denisSolution

Hi, I'm Denis, a full-stack developer experienced with live systems managing interconnected features across permissions, workflows, and data handling. I understand your situation. You have 58 issues spanning document handling, permissions, billing, UI, and workspace logic that need methodical execution through your Trello board, careful GitHub implementation, and iterative testing. This work prioritizes consistency and communication over speed. I've tackled similar large issue backlogs on established codebases where each fix requires testing and validation before proceeding. The key is quickly understanding your architecture, then working through items systematically without introducing new problems. My approach is straightforward: First, I'll review your issue list and codebase to understand the structure and organizational patterns. Then I'll work through assigned issues in batches, prioritizing items that unblock others. Each fix gets implemented on a branch, tested locally, and submitted as a pull request with clear descriptions. After your development server testing and feedback, I'll make adjustments and move forward. I'll pay special attention to issue context and dependencies, especially around permissions, workflows, and state management. I'll map these upfront rather than fixing things in isolation. I can start immediately. Let's connect and discuss the details. Thanks, Denis.

@hassanmustafa01

Hello. The hardest part of this Termp update and bug fix project is managing and prioritizing a large backlog of 58 diverse issues across PDF/DOCX processing, permissions, workflows, analytics, and billing without disrupting the live development environment. I will follow your GitHub branch + Pull Request workflow and Trello issue tracking to: 1. Audit and categorize the CSV and Trello issues to create a clear priority list. The first deliverable will be a detailed fix plan with issue grouping and estimated effort. 2. Fix PDF upload and DOCX spacing/segmentation bugs, then address permission and workflow completion issues. 3. Improve analytics, UI, and translation workspace features, followed by billing and subscription fixes. 4. Submit PRs for each batch, deploy to your dev server, and iterate based on your testing feedback. I recently resolved complex document workflow and permission bugs for a SaaS translation tool, improving stability and user role enforcement. I also fixed PDF export and UI glitches in a multi-user environment, similar to your stack and process. Please share repo access and Trello board details to begin the initial audit and plan. Looking forward to your reply.

@Tacticssoft

Hi, I’m an experienced Full-Stack Developer and can work through your 58 open issues systematically and reliably. I’m comfortable working with existing production codebases, debugging complex workflows, fixing permissions, and implementing feature improvements without breaking existing functionality. I can review each Trello issue carefully, reproduce the problem, implement the fix, and test it before submitting a Pull Request. I’ll work within your GitHub branch and PR workflow and deploy my branch to the development environment for live testing. I can handle issues involving PDF/DOCX processing, translation workflows, roles and permissions, analytics, exports, billing, subscriptions, and UI improvements. I’ll also investigate related edge cases so fixes are stable rather than simply addressing the visible symptom. Clear commits, organized changes, proper testing, and regular progress updates will be maintained throughout the engagement. I’m comfortable responding to testing feedback and making additional adjustments until each assigned issue is confirmed complete. I can start quickly, review the CSV and Trello backlog, and help prioritize the issues based on complexity and dependencies. I’d be happy to discuss the existing stack and begin with a small batch of issues to establish the workflow before moving through the remaining backlog.

@Sv3nie

Hi, Is the app on Node and React? Fixing bugs in existing JavaScript code is my main work, I'd take the Trello list issue by issue via PRs. Lets get in contact first.

@sabaehsan

Greetings, I see that you're looking for someone to tackle a range of bug fixes and feature updates in your development environment, with 58 open issues to address. My approach would involve diving into the Trello board to get a clear understanding of each issue. From there, I’d focus on making the necessary adjustments in a systematic way, ensuring that each fix is thoroughly tested before submitting a Pull Request. My background in JavaScript and software development equips me to handle the variety of issues you listed, from document workflow bugs to role permission fixes. I’m comfortable with the GitHub branch and pull request workflow, so collaboration and communication will be seamless as we work through these updates together. Looking forward to bringing your project to completion. Best regards, Saba Ehsan

@msaqibimran

Hi, I can help resolve the 58 open issues in your development environment efficiently. Based on the sample items you provided, I estimate it will take around 3-4 weeks to address the major bugs and feature updates, depending on their complexity. Are there any specific high-priority issues you want to tackle first? Additionally, do you have a testing process in place that I should follow after implementing the fixes? I plan to work through each ticket on your Trello board, ensuring that bugs are fixed and updates are tested directly in the development environment. Continuous feedback will help refine the solutions until each issue is resolved. With experience in PHP/Laravel and handling similar projects, I understand the importance of delivering reliable updates. Let's discuss the details to finalize the timeline and scope. Best regards, Mohammad

@ianb65

Hi there, Termp update and bug fix across 58 open issues in your live development environment needs disciplined triage, root-cause fixes, and clean GitHub branch work. I have strong hands-on experience with Software Development and have solved similar problems involving Development workflows and GitHub-based delivery. My approach would be to: * Review the existing code, architecture, logs, or current implementation. * Identify the root cause and determine what can be reused versus what needs to be changed. * Implement a clean, maintainable solution using Java and sound Software Architecture. * Test edge cases, reliability, performance, security, and integration behavior. * Deploy or integrate the fix without disrupting the existing system. For a backlog like this, preserving backward compatibility while fixing workflow, permissions, and document-processing regressions is critical. I prefer fixing the actual root cause rather than applying temporary patches, and I will keep the implementation simple, stable, and maintainable. I can start by reviewing the Trello board, CSV issue list, and current setup and proceed with the most practical solution. Best regards, Ian

@MIndlabsAi6

With over 20 years of experience in the software development field, I have a broad skill set that perfectly aligns with the needs of this project. Whether it's mobile app development, reverse engineering, or SaaS and cloud systems, I have the necessary knowledge and proficiency to tackle your 58 open issues with precision. My deep understanding of low-level C/C++, native system components, APIs, databases and more make me uniquely suited to address and resolve any technical issues you may be facing. Additionally, my expertise extends to web scraping and automation, which could prove invaluable when it comes to managing your extensive list of tasks. I eagerly anticipate the opportunity to work on these issues with your development team using your preferred GitHub branch + Pull Request workflow. My aim is simple: provide clean engineering and deep technical understanding to ensure your software performs impeccably in the real world. Selecting my services would give you 100% commitment to excellence from a seasoned professional who values reliability above all else.

@lazarr4

Hello, I can address the 58 open issues by prioritizing critical bugs first, then implementing updates in a structured workflow to minimize regression risks. I’ve fixed similar issues for a SaaS client—first addressing PDF rendering bugs, then improving translation workflows, which reduced support tickets by 40%. The key was isolating changes to avoid breaking dependencies. I’d approach this by: - Grouping fixes by feature area (e.g., PDF handling, permissions) to streamline testing. - Using feature flags for non-critical updates to deploy safely. - Automating regression checks for core workflows to catch issues early. This will reduce downtime and improve user experience by ensuring fixes align with existing functionality. After completing the fixes, I’ll provide a summary of changes and testing steps to confirm everything works as expected. If this approach fits your needs, I’d be happy to review the Trello board and start planning the implementation. Thanks, Lazar.

@codeandcommand

I have handled bug fixes and feature updates on live dev environments before, mostly the tricky part where testing catches regressions before they hit production. I would pull the repo, go through open issues on GitHub, and knock out fixes in order of priority. Can start today, first batch ready in 3 days. Budget and timeline here are based on the post as written. Once we go through the actual issue list, the real scope might turn out bigger, so numbers may shift. Want me to send a quick scope doc so we can get moving?

@MSaadJaved

Hi, I can work through the 58-item Termp backlog on your live development branch, covering the CSV/Trello issues, GitHub PR workflow, and dev deployment for testing. The main technical concern is that several items span workflow, permissions, file handling, and billing states, so I’ll trace each bug from the existing behavior to the affected code path before patching. I recently fixed a similar mix of document workflow and permission issues in a live SaaS app, including export/viewer bugs and role-based access edge cases. For your project, I’d begin by reviewing the Trello board and CSV together, reproducing the highest-impact defects, then implement fixes with verification on the development server. Which issue category is currently causing the most disruption for your team? Best regards, NexLoom

@amadorjay

Hi there, The hard part is not just fixing the bugs; it’s ensuring each fix aligns with the overall project workflow and does not introduce new issues. With 58 open items, prioritizing which issues to tackle first is crucial to maintain momentum. Your GitHub branch and Pull Request workflow is clear, and I can immediately start addressing high-impact issues like the PDF export and DOCX viewer fixes, which often affect user experience significantly. Could you clarify if there’s a specific timeline for addressing these issues, or should I focus on the highest priority items first? Thank you.

@MuhammadAkif8

Can you provide access to the Trello board so I can review the 58 issues and prioritize the fixes based on their dependencies? The main challenge is resolving interconnected workflow, permissions, document handling, billing, and UI bugs without introducing regressions across the live development environment. I will work issue by issue on a dedicated GitHub branch, reproduce each problem, implement the fix, test related flows, and submit focused Pull Requests. I will deploy changes to the development server for your testing and handle follow up fixes until each assigned item meets the stated requirements. Best regards, Akif U